In order to complete this lesson you will need:
In this lesson we will:
At this stage, you have already quality assured your code and generated a production-ready deployment artifact. We will now deploy that artifact to a production environment on Acquia Cloud.
You should always backup your production database prior to a release, even if you’re entirely confident in the code that you’re releasing. Acquia Cloud provides a simple interface for quickly creating environment specific backups.
Next we’ll take your Git tag and deploy it to the production environment. There are a few ways to do this:
You can use the Acquia Cloud interface to deploy the Git tag to your production environment:
Acquia Cloud provides a set of Drush commands that allow you to interact with your application via the CLI. These commands are installed when you download your Drush aliases from Acquia Cloud.
You may use these to deploy your new tag to your production environment. This can be particularly helpful if you would like to script your deployments.
drush @myapp.prod ac-code-path-deploy 1.0.0
If this is your first release on Acquia Cloud, you should take this opportunity to put your site into production mode. In Production mode, you cannot copy your files or database to your Production environment. This protects you from possibly destroying your live application by overwriting the live Production files and databases.