require 'recipe/magento2.php';Deployer is a free and open source deployment tool written in PHP. It helps you to deploy your Magento 2 application to a server. It is very easy to use and has a lot of features.
Three main features of Deployer are:
- Provisioning - provision your server for you.
- Zero downtime deployment - deploy your application without a downtime.
- Rollbacks - rollback your application to a previous version, if something goes wrong.
Additionally, Deployer has a lot of other features, like:
- Easy to use - Deployer is very easy to use. It has a simple and intuitive syntax.
- Fast - Deployer is very fast. It uses parallel connections to deploy your application.
- Secure - Deployer uses SSH to connect to your server.
- Supports all major PHP frameworks - Deployer supports all major PHP frameworks.
You can read more about Deployer in Getting Started.
The deploy task of Magento 2 consists of:
- deploy:prepare – Prepares a new release
- deploy:info – Displays info about deployment
- deploy:setup – Prepares host for deploy
- deploy:lock – Locks deploy
- deploy:release – Prepares release
- deploy:update_code – Updates code
- deploy:env – Configure .env file
- deploy:shared – Creates symlinks for shared files and dirs
- deploy:writable – Makes writable dirs
- deploy:vendors – Installs vendors
- deploy:clear_paths – Cleanup files and/or directories
- deploy:magento – Magento2 deployment operations
- magento:build – Magento2 build operations
- magento:compile – Compiles magento di
- magento:deploy:assets – Deploys assets
- magento:maintenance:enable-if-needed – Set maintenance mode if needed
- magento:config:import – Config Import
- magento:upgrade – Run upgrades if needed
- magento:maintenance:disable – Disables maintenance mode
- magento:build – Magento2 build operations
- deploy:publish – Publishes the release
- deploy:symlink – Creates symlink to release
- deploy:unlock – Unlocks deploy
- deploy:cleanup – Cleanup old releases
- deploy:success – Deploys your project
In addition the Magento 2 recipe contains an artifact deployment. This is a two step process where you first execute
bin/dep artifact:build [options] [localhost]to build an artifact, which then is deployed on a server with
bin/dep artifact:deploy [host]The localhost to build the artifact on has to be declared local, so either add
localhost()
->set('local', true);to your deploy.php or
hosts:
localhost:
local: trueto your deploy yaml.
The artifact:build command of Magento 2 consists of: * build:prepare – Prepare local artifact build
- build:remove-generated – Clears generated files prior to building.
- deploy:vendors – Installs vendors
- magento:compile – Compiles magento di
- magento:deploy:assets – Deploys assets
- artifact:package – Packages all relevant files in an artifact.
The artifact:deploy command of Magento 2 consists of:
- artifact:prepare – Prepares an artifact on the target server
- deploy:info – Displays info about deployment
- deploy:setup – Prepares host for deploy
- deploy:lock – Locks deploy
- deploy:release – Prepares release
- artifact:upload – Uploads artifact in release folder for extraction.
- artifact:extract – Extracts artifact in release path.
- deploy:additional-shared – Adds additional files and dirs to the list of shared files and dirs
- deploy:shared – Creates symlinks for shared files and dirs
- deploy:writable – Makes writable dirs
- magento:maintenance:enable-if-needed – Set maintenance mode if needed
- magento:config:import – Config Import
- magento:upgrade – Run upgrades if needed
- magento:maintenance:disable – Disables maintenance mode
- deploy:symlink – Creates symlink to release
- artifact:finish – Executes the tasks after artifact is released
- magento:cache:flush – Flushes Magento Cache
- cachetool:clear:opcache – Clears OPcode cache
- deploy:cleanup – Cleanup old releases
- deploy:unlock – Unlocks deploy
- deploy:success – Deploys your project
The magento2 recipe is based on the common recipe.
Configuration
By default setup:static-content:deploy uses en_US.
To change that, simply put set('static_content_locales', 'en_US de_DE');
in you deployer script.
'en_US'Configuration
You can also set the themes to run against. By default it'll deploy
all themes - add('magento_themes', ['Magento/luma', 'Magento/backend']);
If the themes are set as a simple list of strings, then all languages defined in static_content_locales are
compiled for the given themes.
Alternatively The themes can be defined as an associative array, where the key represents the theme name and
the key contains the languages for the compilation (for this specific theme)
Example:
set('magento_themes', ['Magento/luma']); - Will compile this theme with every language from static_content_locales
set('magento_themes', [
'Magento/luma' => null, - Will compile all languages from static_content_locales for Magento/luma
'Custom/theme' => 'en_US fr_FR' - Will compile only en_US and fr_FR for Custom/theme
'Custom/another' => 'static_content_locales it_IT' - Will compile all languages from static_content_locales + it_IT for Custom/another
]); - Will compile this theme with every language
[
]Static content deployment options, e.g. '--no-parent'
Deploy frontend and adminhtml together as default
falseUse the default languages for the backend as default
'{{static_content_locales}}'backend themes to deploy. Only used if split_static_deployment=true This setting supports the same options/structure as magento_themes
['Magento/backend' => null]Configuration
Also set the number of concurrent jobs to run. The default is 1
Update using: set('static_content_jobs', '1');
'1'return time();Magento directory relative to repository root. Use "." (default) if it is not located in a subdirectory
'.'Overrides shared_files from recipe/deploy/shared.php.
[
'{{magento_dir}}/app/etc/env.php',
'{{magento_dir}}/var/.maintenance.ip',
]Overrides shared_dirs from recipe/deploy/shared.php.
[
'{{magento_dir}}/var/composer_home',
'{{magento_dir}}/var/log',
'{{magento_dir}}/var/export',
'{{magento_dir}}/var/report',
'{{magento_dir}}/var/import',
'{{magento_dir}}/var/import_history',
'{{magento_dir}}/var/session',
'{{magento_dir}}/var/importexport',
'{{magento_dir}}/var/backups',
'{{magento_dir}}/var/tmp',
'{{magento_dir}}/pub/sitemap',
'{{magento_dir}}/pub/media',
'{{magento_dir}}/pub/static/_cache',
]Overrides writable_dirs from recipe/deploy/writable.php.
[
'{{magento_dir}}/var',
'{{magento_dir}}/pub/static',
'{{magento_dir}}/pub/media',
'{{magento_dir}}/generated',
'{{magento_dir}}/var/page_cache',
]Overrides clear_paths from recipe/deploy/clear_paths.php.
[
'{{magento_dir}}/generated/*',
'{{magento_dir}}/pub/static/_cache/*',
'{{magento_dir}}/var/generation/*',
'{{magento_dir}}/var/cache/*',
'{{magento_dir}}/var/page_cache/*',
'{{magento_dir}}/var/view_preprocessed/*',
]'{{release_or_current_path}}/{{magento_dir}}/bin/magento'// detect version
$versionOutput = run('{{bin/php}} {{bin/magento}} --version');
preg_match('/(\d+\.?)+(-p\d+)?$/', $versionOutput, $matches);
return $matches[0] ?? '2.0';:::info Autogenerated The value of this configuration is autogenerated on access. :::
:::info Autogenerated The value of this configuration is autogenerated on access. :::
//Some conditions, such as new RabittMQ services require a full upgrade and are not detecet by setup:db:status
//TODO: Add checks, once implemented, for detecting necessary full upgrade process. See future RabbitMQ Check: https://github.com/magento/magento2/pull/39698
return false;:::info Autogenerated The value of this configuration is autogenerated on access. :::
Deploy without setting maintenance mode if possible
trueArtifact deployment section The file the artifact is saved to
'artifact.tar.gz'The directory the artifact is saved in
'artifacts'Points to a file with a list of files to exclude from packaging.
The format is as with the tar --exclude-from=[file] option
'artifacts/excludes'If set to true, the artifact is built from a clean copy of the project repository instead of the current working directory
falseOverrides repository from recipe/common.php.
Set this value if "build_from_repo" is set to true. The target to deploy must also be set with "--branch", "--tag" or "--revision"
nullThe relative path to the artifact file. If the directory does not exist, it will be created
if (!testLocally('[ -d {{artifact_dir}} ]')) {
runLocally('mkdir -p {{artifact_dir}}');
}
return get('artifact_dir') . '/' . get('artifact_file');The location of the tar command. On MacOS you should have installed gtar, as it supports the required settings :::info Autogenerated The value of this configuration is autogenerated on access. :::
Array of shared files that will be added to the default shared_files without overriding
Array of shared directories that will be added to the default shared_dirs without overriding
Compiles magento di.
Tasks
To work correctly with artifact deployment, it is necessary to set the MAGE_MODE correctly in app/etc/config.php
e.g.
'MAGE_MODE' => 'production'Deploys assets.
To work correctly with artifact deployment it is necessary to set system/dev/js , system/dev/css and system/dev/template
in app/etc/config.php, e.g.:
'system' => [
'default' => [
'dev' => [
'js' => [
'merge_files' => '1',
'minify_files' => '1'
],
'css' => [
'merge_files' => '1',
'minify_files' => '1'
],
'template' => [
'minify_html' => '1'
]
]
]Deploys assets for backend only.
Deploys assets for frontend only.
Syncs content version.
Enables maintenance mode.
Disables maintenance mode.
Set maintenance mode if needed.
Config Import.
Upgrades magento database.
Run upgrades if needed.
Flushes Magento Cache.
Magento2 deployment operations.
This task is group task which contains next tasks:
- magento:build
- magento:maintenance:enable-if-needed
- magento:config:import
- magento:upgrade
- magento:maintenance:disable
Magento2 build operations.
This task is group task which contains next tasks:
Deploys your project.
This task is group task which contains next tasks:
Run magento post deployment failure tasks.
Run Magento Deployment Failure Tasks
This task is group task which contains next tasks:
Packages all relevant files in an artifact.
tasks section
Uploads artifact in release folder for extraction.
Extracts artifact in release path.
Clears generated files prior to building.
Prepare local artifact build.
Builds an artifact.
This task is group task which contains next tasks:
- build:prepare
- build:remove-generated
- deploy:vendors
- magento:compile
- magento:deploy:assets
- artifact:package
Adds additional files and dirs to the list of shared files and dirs.
Update cache id_prefix.
Update cache id_prefix on deploy so that you are compiling against a fresh cache Reference Issue: davidalger/capistrano-magento2#151 To use this feature, add the following to your deployer scripts:
after('deploy:shared', 'magento:set_cache_prefix');
after('deploy:magento', 'magento:cleanup_cache_prefix');Cleanup cache id_prefix env files.
After successful deployment, move the tmp_env.php file to env.php ready for next deployment
Remove cron from crontab and kill running cron jobs.
Remove cron from crontab and kill running cron jobs To use this feature, add the following to your deployer scripts:
after('magento:maintenance:enable-if-needed', 'magento:cron:stop');Install cron in crontab.
Install cron in crontab To use this feature, add the following to your deployer scripts:
after('magento:upgrade', 'magento:cron:install');Prepares an artifact on the target server.
This task is group task which contains next tasks:
- deploy:info
- deploy:setup
- deploy:lock
- deploy:release
- artifact:upload
- artifact:extract
- deploy:additional-shared
- deploy:shared
- deploy:writable
Executes the tasks after artifact is released.
This task is group task which contains next tasks:
Actually releases the artifact deployment.
This task is group task which contains next tasks: