Magento 2 git deployment

March 4, 2022 . 2 MIN READ

For Initialisation and Installation follow the steps from Alex his answer for most of the steps, only differences I would recommend:

Git configuration

Only store the following files in your Git repository:

json
lock
app/etc/config.php

For your project custom code, also use separate modules that you include thru composer. Managing this thru composer is easier as you can lock a specific version/release that you want to deploy. This also forces you to use the same approach for internal and external modules.

Deployment

During development you update the modules on your environment (dev/test) with the command:

composer update

This will update the composer.lock file with the versions installed on that installation.

On staging/pre-production/production you can create/install the same setup with the command:

git pull

composer install

This will install all the same modules as used in dev/test to ensure that the testing before publishing to production is done with the same module versions as it is developed with.

After the installation to run the following commands:

bin/magento setup:upgrade

bin/magento setup:di:compile (or setup:di:compile-multi-tenant)

bin/magento setup:static-content:deploy

This will update the database (schema and data upgrade), generate the DI configuration and deploy all static view files.

frontend-setup steps

In order for these scripts to work set your shop to production mode in your env.php and setup your theme in dev/tools/grunt/configs/themes.js. (the following steps were put into an ansible playbook)

delete var/cache
delete var/view_preprocessed
delete pub/static/*(don’t delete the .htaccess)
delete var/composer_home
run php bin/magento cache:flush
run php bin/magento setup:static-content:deploy %your_languages%
delete all themes/languages you don’t actually use from pub/static/frontend
remove hard-copies of less files from pub/static/frontend
run php bin/magento dev:source-theme:deploy –locale=”%your_language%” –theme=”%your_theme%” css/styles-m css/styles-l css/email css/email-inline
optional: we use a bash-script to change the absolute symlinks, created in step 9, into relative ones, making it possible to run grunt from outside the vm
run grunt less:your_theme