How Acquia Dev Desktop works with Acquia Cloud

Acquia Dev Desktop is integrated with Acquia Cloud. You can export websites created in Acquia Dev Desktop into your Acquia Cloud subscription or make a local clone of your Acquia Cloud websites with a couple of clicks. Then, you can easily sync the local and Acquia Cloud versions of your sites, pushing changes up to the cloud and pulling them down to your local version. This page describes what's happening when you use Acquia Dev Desktop with Acquia Cloud sites.

This is just for your information; Acquia Dev Desktop does all this automatically for you. You can see a step-by-step log of these actions by clicking More in the progress dialog.

Viewing more info in a progress dialog

When you host a local site on Acquia Cloud

When you use Acquia Dev Desktop to host a local site on Acquia Cloud, Acquia Dev Desktop:

  1. Creates a site archive from your local site, using the drush archive-dump command. If the local site is a Drupal multisite, only the selected multisite is included.
  2. Uploads the archive to Acquia Cloud using SFTP.
  3. Connects to your Acquia Cloud using SSH and runs drush ah-site-archive-import to import the uploaded archive into your Acquia Cloud subscription.
  4. Downloads site code from your code repository to a new docroot folder (using git clone).
  5. Modifies settings.php in the new local site to connect to the existing database.
  6. Copies files (and the additional multisites, if any) from the old docroot to the new one.

When you make a local clone of an Acquia Cloud site

When you use Acquia Dev Desktop to make a local clone of an Acquia Cloud site, Acquia Dev Desktop:

  1. Downloads the site code from your Acquia Cloud code repository to a new docroot folder (using git clone).
  2. If the Acquia Cloud site contains multisites, Acquia Dev Desktop asks you which multisite to clone now.
  3. Creates a new local database and modifies the site’s settings.php to connect to the new database.
  4. Imports the database from Acquia Cloud. To do so, it connects to the Acquia Cloud server using SSH, runs drush sql-dump, downloads the resulting database archive using SFTP, and then imports the downloaded database into the new local database.
  5. Downloads the Acquia Cloud site's files using rsync. The synced folders are: [docroot]/files, [docroot]/sites/all/files, and [docroot]/sites/[selected multisite]/files.
  6. Gets the drush aliases associated with the site, using the Cloud API, and saves them locally to the [user home]/.acquia/DevDesktop/Drush/Aliases directory.

When you push local code to Acquia Cloud

  • If you have a tag deployed locally and have no local modifications, Acquia Dev Desktop deploys the same tag on the Acquia Cloud environment and finishes the push operation.
  • If you have a tag deployed locally and have made local modifications to the code, Acquia Dev Desktop displays an error. You can't deploy to a tag.
  • If you have a branch deployed locally and have made local modifications, Acquia Dev Desktop presents you with a list of local modifications and asks what to do with them. See Committing local changes to Acquia Cloud for more information.
  • Acquia Dev Desktop applies the selected changes, pushing changed files to the code repository, and adding any designated files to the ignore list.

When you push a local database to Acquia Cloud

When you push a local database to Acquia Cloud, Acquia Dev Desktop:

  1. Creates a dump file from the local database using drush sql-dump.
  2. Uploads the database dump to Acquia Cloud using SFTP.
  3. Connects to the Acquia Cloud site using SSH and runs drush sql-drop to drop the old database.
  4. Imports the uploaded database dump file into the Acquia Cloud site's database.

When you push local files to Acquia Cloud

Acquia Dev Desktop uploads the local site's files to Acquia Cloud using rsync. The synced folders are: [docroot]/files, [docroot]/sites/all/files, and [docroot]/sites/[selected multisite]/files.

When you pull code from Acquia Cloud

  • If you have a tag deployed locally and it matches what is deployed in the Acquia Cloud environment, then Acquia Dev Desktop returns an error.
  • If you have a branch deployed locally and it matches what is deployed in the Acquia Cloud environment, then Acquia Dev Desktop updates the local code from the version control system (using git pull ).
  • If the local and Acquia Cloud branches (or tags) don’t match and your version control system is Git, then Acquia Dev Desktop switches the local branch to use what's deployed on the Acquia Cloud environment (same as git checkout).

When you pull a database from Acquia Cloud

When you pull a database from Acquia Cloud, Acquia Dev Desktop:

  1. Connects to Acquia Cloud using SSH and creates a remote database dump file by running drush sql-dump.
  2. Downloads the database dump file from Acquia Cloud using SFTP.
  3. Runs drush sql-drop to drop the existing local database.
  4. Imports the downloaded dump file into the local database.

When you pull files from Acquia Cloud

Acquia Dev Desktop downloads the Acquia Cloud site's files using rsync. The synced folders are: [docroot]/files, [docroot]/sites/all/files, and [docroot]/sites/[selected multisite]/files.

For more information about syncing local and Acquia Cloud sites, see:

Contact supportStill need assistance? Contact Acquia Support