Co-Authored-By: Kundan <198781+kundancool@users.noreply.github.com>
Co-authored-by: Kundan <198781+kundancool@users.noreply.github.com>
Co-authored-by: Anton Medvedev <anton@medv.io>
* Remove deploy:public_disk task
Redundant since this can be achieved with the `artisan:storage:link` task since 5.3.
5.2 support was dropped in June 2016 so it is safe to stop supporting it ourselves.
* Remove publish artisan commands
These commands are made to generate some code that should then be committed and pushed. These should never be needed directly in production.
* Add and rename artisan tasks
* Refactor artisan command registration
* Revert "Refactor artisan command registration"
Doesn't work nicely with docgen 😭
* Update laravel.md
Now, it should not matter what default shell is used on a server: zsh, fish.
Deployer will automatically switch to bash (or to a user-specified shell).
Laso added a release verification task.
* 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>
Created new container using Ubuntu 20.04 as a base, for a E2E test
environment for the provision recipe.
Due to container sharing a kernel with host os, the firewall provisioning
had to be turn off during the testing procedure.
