The one with Jira API fixes

Jira's API changed, we changed.

todo: we should probably use the accountId to filter going forward, but this is a quick fix that works.

The one with php 7.4

• documentation fixes @shakyShane 58fbecc
• added php 7.4 support @shakyShane e62f046
• Update varnish image @mikeymike a44438f

The one with documentation links

Documentation (a work in progress)

• added documentation + links in the --help output 3bf4364

Example
Any command ending with --help will show a certain amount of helpful information for that particular
command, but now when you run this, you'll also get a link to the latest documentation.

wf2 up --help

[m2] Bring up containers

USAGE:
    wf2 up [FLAGS]

FLAGS:
    -a, --attached    Run in attached mode (streaming logs)
    -c, --clean       stop & remove other containers before starting new ones

Documentation:
    https://docs.rs/wf2_core/latest/wf2_core/recipes/m2/subcommands/up/index.html

The docs are one of the easiest way to contribute to the project, so feel free to send a PR if you see
something that can be improved

---

New env init command

• added support for a wf2.env.yml file. This file accepts any values found in the normal file, but these will take preference - it's a way to allow temporary overrides in configuration. 834ba0e

Example

Take a regular wf2.yml...

# wf2.yml
domains: [acme.m2]
php_version: 7.2

...then run wf2 env init & override the php_version in the new file that it creates...

# wf2.env.yml
php_version: 7.3

... now when you run up or any other command, wf2 will get the merged values, like so:

# what wf2 sees:
domains: [acme.m2]
php_version: 7.3

One thing to note, the implementation is very simplistic for the MVP, so any top-level keys will cause that entire value to be overriden.

---

Added the -v flag to down 788d664

• allow volumes to also be deleted when running wf2 down

# deletes all containers, networks and volumes
wf2 down -v

The one with `enterprise` support in m2-playground

To support enterprise projects in the m2-playground, 2 changes needed to happen

1. introduce a new flag -e to instruct wf2 to setup an enterprise project
2. allow public/private keys to be used once, but not override existing ones

Since most developers will have there own personal public & private keys saved in wf2, we needed to allow a one-time set of keys to be used, but to NOT override your personal ones.

wf2 m2-playground 2.3.4 --username 123456 --password 654321 -e

v0.26.0

Bug fixes

• fix: version upgrades can cause file collisions - #85
  This addresses situations where output files (docker-compose, nginx conf etc) are changed across releases - now, every time you run wf2 up, the local wf2 directory will be completely wiped.

• fix: forward error message when inside a Sequence #89
  Particular 'readiness' checks were not correctly forwarding their human-readable errors

Features

• feat: Show a diff when app/etc/env.php.dist has changed from app/etc/env.php #90
  If env.php & env.php.dist both exist, but are different, you get a warning when running wf2 up - the problem is the warning doesn't say 'what' changed, so people are just blindly skipping past it. This change will output a coloured diff above the question now, to make it easier to see what you're agreeing to

the one with fixes for `fastcgi_buffers`

Just a single change #83

The one with DX improvements

More useful wf2 up

wf2 up will no longer attach to the docker-compose stream. That was mostly
done to aid debugging in the early days.

Because of this, we can now show a nice message when up is complete (see below),
but if you really want or need the old behaviour, simply provide -a.

# will no-longer stream docker-compose logs
wf2 up

# if you want the old behaviour
wf2 -a

NEW automatic clone of env.php.dist

When you run wf2 up on any M2 project, it will now check if env.php is missing + there's a env.php.dist, then it will copy env.php.dist -> env.php without needing any user input.

This, combined with the new requirement that all M2 projects contain a valid env.php.dist should mean
that getting setup on a project will be even smoother.

NEW sql command for M2

Added the sql command to the m2 recipe to allow queries to be directly executed
in the db service.

wf2 sql "select * from core_config_data"

NEW --clean flag for wf2 up

Added the --clean flag to up, it's just a safe convenience for stopping all previous containers
before starting new ones. This can be handy when switching between projects/playgrounds

# this...
wf2 up --clean

# is basically like doing
docker stop $(docker ps -aq)
docker rm $(docker ps -aq)
wf2 up

M2 is no longer the 'default' recipe

Since wf2 now has some global commands, it doesn't make sense to always select a recipe... so
it no longer does. This opens the door for more/bigger global commands & features.

NEW --recipe flag

Added the --recipe flag to allow you to explore what wf2 can do, without being in a folder
with a wf2.yml file. For example, you may just be curious and want to read the help screens
for different recipes. Well now you can

# See JUST M2 help, from anywhere
wf2 --recipe M2 --help

# See JUST Wp help
wf2 --recipe Wp --help

This is really useful for debugging how wf2/docker work, since you can combine --recipe with --dryrun.

# take a peak at how db-import works for M2, without even being in an M2 project
wf2 --recipe M2 --dryrun db-import shane.sql

NEW expose the RabbitMQ Management UI

This always existed, but the mapping was not setup in the Traefik config... But now is, and
when you run wf2 up you'll see the address to access it on.

NEW beta Wp recipe + Playground

Added a BETA Wp recipe - mostly for proving the whole 'recipe' concept and proving that all features
work & can be scoped to a recipe.

Right now the playground works well - it will setup Wordpress + Bedrock exactly how we use it at JH,
but further refinement is needed to ensure wf2 up on our existing WP sites works correctly.

wf2 wp-playground

CI changes/improvements

We have now fully migrated to GH Actions for build/linting/testing & releases.

v0.25.1: Merge pull request #80 from WeareJH/output-fixes

feat: `--clean` flag

The one that finally fixes automated asset release

GH release == Asset auto build and upload 👌

???????

???????