* removed incorrect duplicate version column
Output is as follows so:
$plugin,$label,$version,$upgrade,$author,$installed,$active,$upgradeable,
Shopware Plugin Service
=======================
------------------- --------------------------------------------------------- --------- ----------------- --------------------------- ----------- -------- -------------
Plugin Label Version Upgrade version Author Installed Active Upgradeable
------------------- --------------------------------------------------------- --------- ----------------- --------------------------- ----------- -------- -------------
BuckarooPayments Buckaroo Payment 1.1.1 Buckaroo Yes Yes No
DevTools Additional tools to support your Shopware 6 development 0.2.0 Maurits Meester Yes Yes No
* Invoke sw:plugin:refresh inside sw:plugin:activate:all instead of incorrectly redefining it
* Upgrade all plugins that are upgradeable
* Changelog update
* Ran docgen
* Do NOT make upgrading all default
* Update doc
Co-authored-by: Fabian Blechschmidt <github@fabian-blechschmidt.de>
Co-authored-by: Fabian Blechschmidt <blechschmidt@fabian-blechschmidt.de>
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>
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
* #2423 shopware: task sw:plugin:activate:all runs migration script in wrong order
- add dependency for polyfill (to use str_ends_with)
- marcj/topsort (for sorting the shopware modules)
* #2423 shopware: task sw:plugin:activate:all runs migration script in wrong order
- get the plugin list
- read the composer names and dependencies from composer.lock
- order by dependencies
- use sorted list for activation and migration
* #2423 shopware: task sw:plugin:activate:all runs migration script in wrong order
Update changelog
* #2423 shopware: task sw:plugin:activate:all runs migration script in wrong order
do not update doc, but remove require autoload.php
* Safety to avoid modifying files outside deploy_path
Using writable_dirs with writable_use_sudo can lead to a disaster on a server (example using /var/log instead of var/log as writable dir).
* Update writable.php
* Update CHANGELOG.md
* Update CHANGELOG.md
* Update writable.php
* trailing slash
* docgen
* throw exception if absolute path in writable dirs
Composer installer can now take an argument to select which version channel to use: https://github.com/composer/getcomposer.org/pull/156/files
This allows for exemple to stay on major version 1 without specifying a specific Composer version
* 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.
* fixed issue #2209
Copy shared files and folder should be verbose only when deployer is run with Very verbose output
* updated CHANGELOG.md
* changed to -vvv
* changes sprintf to interpolation
