Acquia recommends you have the following working environments, in addition to the RA environment provided by Acquia:
Environment | Description |
---|---|
Production (Prod) | The production environment contains your live code. No testing takes place here, and all production code is ran from a tag, not a branch. |
Staging (Stage) | Acquia uses the staging environment to deploy and test small changes or security updates, and to perform a final test of a development branch or tag before going live. Your staging and production environments should be on the same tag, except when you are testing a new tag on staging for imminent deployment to production. |
Development (Dev) | Active development and testing occurs on your development environment.
Development should be on a branch or master unless you need
the environment for parallel testing. Development branches are merged
into master only when you are ready to test on your staging
environment as a precursor to live deployment on production. |
Remote Administration (RA) | Acquia provides an additional RA environment to facilitate security updates. Acquia uses the RA environment for the proactive process of deploying and testing security updates before deploying them to production. Acquia will overwrite the code and databases on the RA environment on a regular basis. You should use the RA environment only for testing security update branches. For more information about the RA environment, see Environment. |
Acquia recommends your version control system (VCS) workflow has the following attributes:
master
branch should be deployable to production unless updates
are in process. The master
is deployed to your development environment
unless testing is in process.AcquiaRA-2018-02-12-13-14-15
).master
, and update the branch with master
on a regular basis
to ensure the working branch is up-to-date. Depending on the kind of
development on the branch, this may not be possible. During the automated
RA update process, do not merge these changes into master
or deploy
them to production until after the RA update process has completed and the
update branch has been merged back into the main branch.master
, ensuring master
always includes updated code.