* Only set maintenance mode once if needed
Also:
- by adding magento:maintenance:enable-if-needed to the task list instead of invoking it directly, it is now possible to use after() to add custom tasks to be performed in maintenance mode
- the maintenance_mode_status_active check was removed because it is unnecessary and can return wrong results because of caching
* Update docs
* adds sticky to writable recipe
chgrp for all files, chmod g+rwxs for directories, chmod g+rw for files
* adds artifact deployment for magento2 recipe
* Updates Documentation
* removes mode that has been submitted in other MR
* adds divers discussion results from PR #3317
- uses contrib/cachetool
- removes task build:prepare-env
- comments additional_shared_files and additonal_shared_dirs
- avoids invoke()
* updates docs
* corrects additional shared
* expands DocGen for artifact deployment and adds documentation to the magento2 recipe
* corrects missing capital and typo
---------
Co-authored-by: Anton Medvedev <anton@medv.io>
The new [Shopware template](https://developer.shopware.com/docs/guides/installation/template) does not have a `bin/build.sh` file anymore. The missing executable executed `composer install` and `bin/build-js.sh`. Since requiring the new Symfony flex recipe requires running `composer` manually, we just execute `bin/build-js.sh` now.
This could be a breaking change for some users. Don't know if you want to state that somewhere or allow a way to restore the old behavior via flag (although one can just override the `sw-build-without-db:build` task anytime).
* Magento: create variable for bin/magento
so it can be overridden to a custom location
* Update docs
* Allow Magento to be installed in a subdirectory
* Update docs
* Use Magento subdirectory for composer command
* Fix bin/magento call in magento_version function
* Update docs
* Update docs
* Combine magento_dir and bin/magento configurations correctly
* Magento: Fix artifact_path generation
- Fix 1. Add -p parameter to mkdir command
{{artifact_path}} could be configured with multiple folders such as build/artifacts
- Fix 2. run() -> runLocally()
The {{artifact_dir}} is used to keep artifacts archive file.
It should be called at CI server only and not at target server.
Then the task `artifact:upload` uploads this file at target server host under {{release_path}}.
It is not needed to have {{artifact_dir}} at target server.
* Update docs
One of base command to publish your application with Horizon
```
$ php artisan horizon:publish
Copied Directory [/vendor/laravel/horizon/public] To [/public/vendor/horizon]
Publishing complete.
```
* adds sticky and skip mode
Sticky means, that the command-line-user and the http-user are different but share the same group. This mode add a sticky bit to directories and adds writeable for group to all files.
Skip just skips this in case the interactiv user and the http user are equal
* adds comments to file
* updates documentation
* var/page_cache as writable_dirs
It will fix following Zend exception after successful deployment:
Fatal error: Uncaught Zend_Cache_Exception: cache_dir "/path/to/www/releases/7/var/page_cache" is not writable in /path/to/www/releases/7/vendor/magento/zendframework1/library/Zend/Cache.php:209
This exception does not occur on every environment, it depends on PHP pool user/group (default www-data or owner of project directory).
* docgen
* Use correct Git ref spec when `sub_directory` is specified.
The bug is described in detail in issue #3137.
* change variable name for sub-directory target (as requested in PR)
* Add curly braces to domain in Caddyfile
Adding curly braces after the domain name, allows for multiple deploys in the same server.
* regenerate doc for docs/recipe/provision/website.md
Co-authored-by: Victor van Herpt Valdivia <victor@vhvLaptop.lan>
* Update to the lock recipe so that it shows you who currently has the lock on the deployment
* DD#0000: feat: Updated joy test
* DD#0000: feat: Regenerated docs
