Additional Environments
Last updated
Was this helpful?
Last updated
Was this helpful?
Create a development and staging environment for your project to test and demo changes before releasing them in production.
You can select your instance in the User Portal by using the instance drop-down.
The source code will be managed through the same repository that your production environment is managed. Each environment has its own branch within the GitHub project.
The additional environment branches will contain a copy of the current master branch code.
Auth.json is copied over to additional environments from the production environment on creation.
You can create additional environments, such as Staging and Development environments, through the User Portal.
Note that you must be an Owner or Admin to create environments.
Click the New Environment button.
Enter a prefix that will identify the instance, for example, dev. This will be added to the generated instance URL and part of the instance name so you can easily identify it.
Select Region for the instance.
Select Magento mode for the instance. Default and Production modes are available. You can change them later through SSH.
Click Create Environment and after 15 minutes the instance will be available.
During instance creation you will see instance creation progress.
Additional environments are created with the resources listed . If you would like to set different resources please contact .
Media and Database are NOT copied to additional instances from the production environment automatically. A default database and media will be set initially, which may result in your website not working at first due to database data/media and source code inconsistencies. You need to migrate the database and media to an additional environment following these .
This progress will refresh automatically and after the instance is created you will be redirected to the of that instance.
