* Make Magento 2 recipe suitable for push strategy deployments
* updated Magento 2 recipe docs
* Disable task by using disabled()
* Removed push strategy settings, moved build commands to its own group
* Updated docs
Fixes failed deploys when app/etc/config.php is changed with added sites, stores, store views or themes.
Co-authored-by: Fabian Blechschmidt <github@fabian-blechschmidt.de>
* Magento2: look for database migrations in order to get zero downtime deployments when changes are not needed
- also keep maintenance status active in case it was already previously activated
* Magento2: adjust shared dirs
* Magento2: dump autoload before setup di compile
- fix for magento 2.4 deployments https://github.com/magento/magento2/issues/23251
* Magento2: force static content deploy
- avoids deployment failure when magento production mode is not set
* Magento2: update change log
* Magento2: update recipe docs
* Revert "Magento2: force static content deploy"
This reverts commit 45de3337a5a3e524685c422be3fbc6957fe6b480.
* Magento2: detect configuration changes, launch config import
* Magento2: refactor recipe
- make all tasks compatible with any magento 2 version (skip command execution if still does not exist in certain version)
- remove duplicated check on maintenance status
- remove catch for processFailedException
Co-authored-by: Unai Lopez <unai.lopez@vdshop.es>
Co-authored-by: Peter Jaap Blaakmeer <peterjaap@blaakmeer.com>
* Remove magento:enable from Magento 2 recipe
Magento's module states are stored in app/etc/config.php. This task
ignored that and blindly enabled all installed modules.
* Mention the removal of magento:enable in the changelog
