Requirements for Cloud
The following requirements detail technologies, knowledges, accounts, and steps to complete when working with your Magento Commerce code and store in the Cloud.
Prerequisite technologies and knowledges
The following technologies are requirements for developing and deploying your store code:
- Experienced with Git
- Experienced with Composer. For info on how we use Composer, see Compose for Cloud.
- Familiar with Magento 2
- Familiar with Continuous Integration Best Practices
- Understand cloud architecture for Magento Commerce
- Set up a local development environment. Your local workspace works best as a virtual system (VM or container) with all prerequisities installed and the project
masterGit branch cloned. Develop in branches to add modules, extensions, 3rd party integrations, and configurations.
repo.magento.comcredentials in your account
- Obtain an invite by the Account Owner or a super user to the project
Magento Enterprise Cloud Edition does not support the split database performance solution at this time.
We assume you have a good working knowledge of Git. If not, consult the following resources:
Before getting started, make sure you have a Git client installed on your computer to be able to interact with Magento Commerce.
In addition to Git's requirements for valid branch names, Magento Commerce adds two additional requirements:
/character isn't allowed.
- Branch names must be case-insensitively unique. In other words, if you have a branch named
_CaSe_, you cannot create another branch named
You must use Secure Shell (SSH) and not HTTPS to connect to the Git repository. For more information, see GitHub documentation.
Before you test any custom code in your local Magento Commerce environment, you must do all of the following:
- Set the database
Test with the correct file permissions in PRODUCTION mode
Correct permissions only allow write access to
pub/static, pub/media, and
- Test with Redis enabled for page cache and session cache
- Install and configure Fastly
- Test using Varnish for the page cache
Development and testing
For development and testing, we recommend the following:
Test your site in an Integration (development) and Staging (near-production) environment as you complete modifications
You can enable and test individual features, new extensions, and 3rd party integration on different environments prior to merging into a single environment.
You can set an environment variable or enter a CLI command for this specific mode.
- Fully test your site in Staging as a merchant and customer prior to Production deployment
- Verify the Fastly VCL is uploaded to Fastly
- Send a ticket with all storefront domains when going live (to be added to the shared SSL (HTTPS) certificate)
- For custom deploy hooks in Integration, open a Support ticket to have them added to the Staging and Production deployment process
- Profile key flows and customizations using Blackfire.io
License and authentication requirements
The Account Owner creates the initial Magento Commerce (Cloud) account with a purchased subscription. This owner should invite all technical staff, consultants, and Magento partners involved in the code and production of the stores to the project. The invitation provides access to the Git code, environments, and ticketing for the project.
To work with and deploy stores, you need the following:
- Magento Commerce (Cloud) account already created or created via an invitation
- Project invitiation for contributing developers from the Account Owner or a super user
- Magento authentication key for each user who contributes to the project
Your Magento Commerce account must authenticate using any of the following:
- Create your own Cloud account