Deploy your store

The process for deploying and going live with your store in a public or production server in our cloud environment begins with development. To provide the best experience for developing, testing, and deploying your store with consistent configurations we provide an end-to-end solution. Every environment supports direct URL access to the store and Admin console and SSH access for CLI commands.

The following diagram illustrates how the three environments work on a high level:

How test, staging, and production works

  1. You begin in the Integration environment to develop and test your custom modules, Magento extensions, 3rd party integrations, and configurations.
  2. When you push your local development to the Git branch, all of your code, the store, and more are built and deployed directly into an environment.
  3. To fully test in a near-production level environment, you deploy to a Staging environment with full production services. Heavily test in this environment to verify your payment gateways, shipping, price rules, various products, and full customer and admin interactions.
  4. Finally, deploy to the Production environment to complete go live steps and start selling.

Although the Integration environment can have many branches, Staging and Production have only one branch: the deployed Git master.

Assisted deployment

The Staging and Production environments require assisted deployment. These environments are not accessible through the Enterprise Cloud Edition Web Interface to add SSH keys or to modify environment variables, routes, or settings. You must enter a support ticket to deploy code, add SSH keys, and go live.

With SSH keys added, you can access the environments to complete CLI commands without requiring tickets.

Enter a ticket to deploy

For technical reasons, Magento Commerce staging and production systems don’t implement any deployment hooks automatically. These hooks, defined in the hooks section of your .magento.app.yaml file, must be manually migrated to staging or production.

Create a support ticket to let us help you implement any deployment hooks you set up.

Among the settings you can request us to enable are Xdebug and PHPUnit, which assists you in troubleshooting any coding issues you might have during deployment. Because of its memory requirements, we recommend you disable Xdebug before your site is live.

If you have your SSH keys added to Staging and Production environments per a ticket, you can also directly SSH into the environment to use Git CLI commands for deployments.

You can optionally replace the hooks section with a shell script that you can maintain without intervention. You need only to create a support ticket the first time you'd like to use the shell script.

Git and SSH URLs

Locate your Git and SSH URLs from the OneDrive onboarding document you received when you signed up for Magento Commerce.

After you know these URLs, you can access those environments without further intervention.

  • Use the URLs to access the store as a customer.
  • Use the URL /admin to access the Admin panel.
  • Use SSH access and Git CLI commands to deploy updated code to Staging or Production. Magento Cloud CLI commands are not available in Staging and Production.

Read-only environments

You should always deploy code and data from the master branch of your Integration environment to Staging, then to Production. If you need to fix issues, fix them in local development, push to Git, and complete the full deployment.

Next steps

To learn more, check the following: