Skip to content

Releases: WeareJH/wf2

v0.33.3: Merge pull request #127 from WeareJH/elasticsearch-m2-runtime-envs

01 Jun 08:01
23e8986
Compare
Choose a tag to compare

Locked mysql authentication plugin to "mysql_native_password"

04 Feb 10:53
44b03f3
Compare
Choose a tag to compare

Added multistore based on URI prefix support

22 Jan 08:10
49cfe95
Compare
Choose a tag to compare

The one where you can set the mysql image

09 Sep 21:04
Compare
Choose a tag to compare

eg:

domains: [ example.m2 ]
options:
    services:
        db:
            image: "mysql:8.0"

The one with Wordpress fixes

23 Jun 17:51
Compare
Choose a tag to compare

feat: support changing php version for wp 56694b6
fix: prevent name collision when re-using the php service for WP b310bad

The one with PWA support

15 Jun 19:38
Compare
Choose a tag to compare

This release includes includes support for wiring a headless application into the M2 stack.

Benefits:

  • Full M2 Backend stack: PHP, Mysql, MailHog, BlackFire, ElasticSearch, Varnish, Reddis, RabbitMQ etc
  • NodeJS, PM2 -> with all requests going through the M2 stack as they would in production
  • BE developers no longer need ANY tools installed on their machines
  • Easily debug/inovate on things that require both the M2 backend + the PWA
  • production-critical things like Varnish can be fully tested E2E

Configuration

Since (in many cases) the headless application will be in a separate repo, the initial wf2 support requires a tiny bit of configuration - this may be removed/simplifed in the future.

Before:

recipe: M2
domains: [ example.m2 ]

After:

recipe: M2
domains: [ example.m2 ]
options:
  services:
    pwa:
      domains: [ example.pwa, test.ngrok.io ]
      src_dir: /users/shane/pwa
      dockerfile: /users/shane/pwa/wf2/Dockerfile

This assumes that the PWA has a Dockerfile and knows how to build/serve itself.

The one with latest elastic search

12 May 18:45
Compare
Choose a tag to compare
v0.31.1

release: 0.31.1

The one that lets you hack the vendor folder

30 Apr 20:09
Compare
Choose a tag to compare

sync folders from vendor

Sometimes you'll need or want to edit files that would normally be accessible in your local
vendor folder - but you cannot with wf2 because we don't 'sync' 'vendor' by default for performance reasons.

To get around this limitiation, we can add temporary 'sync' folders

with the --sync flag

wf2 up --sync vendor/magento/framework/Acl

You can also add folders with wf2.yml or wf2.env.yml

options:
  services:
    unison:
      ignore_not:
        - vendor/wearejh

Note: If you provide both (in the yml + cli flag) then ONLY the cli flag will be used

The one with n98 and easier mysql imports

03 Apr 07:15
Compare
Choose a tag to compare

The one with MORE jira fixes

19 Feb 21:07
Compare
Choose a tag to compare

Fixed another case where the 'emailAddress' field is absent in some nested api calls. 0a6def5