Single machine deployment
This topic provides instructions for deploying updates to Magento on a production server using the command line.
This process applies to technical users responsible for stores running on a single machine with some themes and locales installed.
Assumptions
- You installed Magento using Composer.
- You are directly applying updates to the server.
This guide does not apply if you used git clone
to install Magento.
Contributing developers should use this guide to update their Magento installation.
Deployment steps
-
Log in to your production server as, or switch to, the file system owner.
-
Change directory to the Magento base directory:
1
cd <Magento base directory>
-
Enable maintenance mode using the command:
1
bin/magento maintenance:enable
-
Apply updates to Magento or its components using the following command pattern:
1
composer require <package> <version> --no-update
package: The name of the package you want to update.
For example:
magento/product-community-edition
magento/product-enterprise-edition
version: The target version of the package you want to update.
-
Update Magento’s components with Composer:
1
composer update
-
Update the database schema and data:
1
bin/magento setup:upgrade
-
Compile the code:
1
bin/magento setup:di:compile
-
Deploy static content:
1
bin/magento setup:static-content:deploy
-
Clean the cache:
1
bin/magento cache:clean
-
Exit maintenance mode:
1
bin/magento maintenance:disable
Alternative deployment strategies
In Magento 2.2, a near-zero downtime deployment model will be available for a variety of complex environments, including Adobe Commerce on cloud infrastructure.
Related topics
- Enable or disable maintenance mode
- Command line upgrade
- Update Magento
- [User Guide: Web Setup Wizard][3]
- [Running the System Upgrade][9]