This is Lesson 3 of Tutorial: Deploying a Drupal Application.
In this next lesson we will deploy a production-ready tagged deployment artifact to a non-production environment on Acquia Cloud Platform.
To complete this lesson you will need:
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 Platform provides an interface for quickly creating environment specific backups.
Next we will take your Git tag and deploy it to a non-Production environment first. In these examples we will use the Dev environment to first show how code can be deployed.
Once you have tested your code from your non-Production deployment thoroughly you can then deploy to the Production environment.
There are a couple of ways to do this:
You can use the Acquia Cloud Platform interface to deploy the Git tag to your environments.
This is an example using the Dev environment:
Acquia Cloud Platform provides a set of Drush commands that allow you to interact with your application via the Command Line Interface (CLI). These commands are installed when you download your Drush aliases from Cloud Platform.
You may use these to deploy your new tag to your environments. This can be particularly helpful if you would like to script your deployments.
drush @myapp.dev ac-code-path-deploy 1.0.0drush @myapp.prod ac-code-path-deploy 1.0.0
If this is your first release on Acquia Cloud Platform, 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.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Wed Oct 22 2025 09:07:31 GMT+0000 (Coordinated Universal Time)