Learn step by step how our zero downtime deployment solution works.
This page will guide you through the deployment process and answer other frequently asked questions about MGT Code Deploy.
Here's how it works:
To start a deployment, log in to the MGT Code Deploy interface where the environment to deploy can be selected on the top right corner.
Next, navigate to "Deployments" and click on the button "New Deployment" where your git username and password need to be entered.
In addition, select a branch or tag to deploy.
At the end of the form, "After Deployment Commands" can be selected, which will be executed after the deployment is completed.
Afterwards, the MGT Code Deploy software starts building the deployment package. The building process of the deployment package consists of the following steps:
1) Cloning the git repository
2) Validating the git repository
3) Executing defined "After Clone Commands" like
setup:di:compile and setup:static-content:deploy for Magento 2
After building the deployment package, MGT Code Deploy ships the deployment package to each instance and waits until all instances are ready.
Finally, all instances get the latest version by switching a symlink. After switching the symlink, we execute the defined "After Switch Commands", for example reloading PHP-FPM.
In the last step, your selected "After Deployment Commands" are executed. For example, these could be commands such as "Clear Magento Cache" or "Purge Varnish Cache".