Add new comment
by Ben Jeavons
It's now easier than ever to get your site setup on the Acquia Network starting with the 2.2 release of the Acquia Network Connector module. Using just your Acquia Network email and password, your subscription credentials will be set and with 1-click you can migrate your entire site to Acquia Cloud.
Previously, Drupal site code and database migrations from one environment to another, such as from your laptop to your server, took several manual steps; and to archive the code and database together required a command line tool like Drush. At this point you're only halfway complete, the archive still must be transfered and your server environment setup for the site.
Migrate to Acquia Cloud with 1 click
With the Acquia Network Connector and a Acquia Network subscription, you can build your site locally or on your own development server and then migrate it to Acquia Cloud with 1 click, no matter the size of site.
The new migrate feature exports your database and builds an archive file of your site, including the files directory. The archive file is then transferred over HTTPS to the dev environment for your hosting site.
- Signup for a free 30-day trial of Acquia Cloud
- Download and enable the Acquia Network Connector module
- Connect your site to your subscription
This 2-minute how-to video shows the process of migrating a small ecommerce site from my computer to Acquia Cloud.
You can try Acquia Cloud free for 30 days.
Some technical details
In the video you'll notice that to connect a site to the Acquia Network I use the email address and password of my Network account. That is a really easy way to setup the Network identifier and key strings used to authenticate to the Network. An email address and password is much easier than copying and pasting, but we don't want to store your Network account email and password on your Drupal site and we don't want to send it as plain-text to Acquia.com in the event your environment doesn't support SSL.
To authenticate your site to the Acquia Network we have to validate the password you provide for the email address by comparing password hashes. Accounts on Acquia Network use unique per-user salts for the stored password hash, so we can't just hash your password on your site and compare, we have to hash using your unique salt. Several server-to-server calls happen after you type in your email and password. The salt for your accounts is retrieved, your password is hashed, and then sent to Acquia.com for validation. Only if valid will your subscription information be returned, and all is monitored for flooding.
The migration process takes a cue from the wonderful Backup & Migrate module by ronan for exporting a database. The archive file is created and compressed then posted over SSL to your Acquia Cloud server in chunks, with unique tokens being exchanged to avoid problems.