Acquia Drupal in version control repositories

Maintaining your site from a version control repository can help your code maintenance workflow. Acquia Drupal is available from three repositories:

• SVN
• Git
• Bazaar (bzr)

Acquia Drupal's Bzr repository is located at: https://code.launchpad.net/~acquia/drupal/1.x-6.x. If you use use Bzr, get a copy with this command:

bzr branch lp:~acquia/drupal/1.x-6.x

Acquia Drupal's Git repository can be cloned with this command:

git clone git://git.acquia.com/drupal/branches/1.x-6.x.git

Acquia Drupal Subversion (SVN) repository - overview

Installing and maintaining Acquia Drupal websites from Acquia's SVN repository is much faster and more reliable than maintaining them by hand. This is because the SVN repository marks all the files it installs and can then make the exact changes needed to the code to update those files.

• Repository location - https://svn.acquia.com/drupal/branches/1.x-6.x

• Installation using SVN - continue reading below.

• Advanced SVN use and known issues - see the Acquia Drupal SVN repository: advanced SVN use and known issues section of this guide.

• Technical support for Acquia Drupal SVN - All registered users of acquia.com are free to participate in the Acquia Drupal Source Code Repositories forum. Check it to see if other users are experiencing similar problems to yours. SVN support questions may also be sent to installer-support@acquia.com.

Learn more about Subversion

The following instructions are limited to a few basic command line commands for installing and updating Acquia Drupal from Acquia's SVN repository. Subversion is, however capable of much more. A great resource for learning more about SVN can be found at: http://svnbook.red-bean.com/en/1.5/.

Installing SVN and SVN GUI clients - For more information on applications that can help you manage SVN repositories, see also the Managing SVN - Options and Applications section of this guide.

Installing Acquia Drupal using Acquia's SVN Repository

These instructions assume you are familiar with basic Drupal, web and server use and that you are comfortable working on the command line.

1. Database ready - You need to have a database, database user and password ready for your new site, just as in any Drupal installation process. More on creating your database here: Install AD from Scratch: Create Database.

2. Login to your server using your own credentials and domain name:

   ssh -l username example.com
    
   

3. Navigate to your [docroot] directory:

   cd [docroot]
   

4. Download latest version of Acquia Drupal to server: - Don't forget the "." at the end of this command!

   svn co https://svn.acquia.com/drupal/branches/1.x-6.x .
   

5. Create required Drupal files, fix permissions

   mkdir ./sites/default/files
   touch ./sites/default/settings.php
   chmod a+rw ./sites/default/settings.php
   chmod a+rwx ./sites/default/files
   

6. Install website - Navigate to http://example.com/install.php (substituting your own domain name for "example.com") in your browser to kick off the Drupal installation process.

Updating Acquia Drupal using the SVN Repository

Non-SVN Drupal sites - For sites installed using the non-svn version of Acquia Drupal, first convert them to the SVN codebase following the instructions in the Advanced SVN use section of this guide.

Update an Acquia Drupal site installed using the SVN repository - Updates are where SVN really shows its strengths. SVN performs seamless critical code updates, so there's no more manual checking of versions or forgetting a file or module. Use the following command:

1. Update your codebase - When you are informed about a new release of Acquia Drupal, navigate to the [docroot] directory on your server and enter the following command:

   svn up
   

2. Run the database update script by navigating to http://example.com/update.php (substituting your own domain name for "example.com") in your browser and following the instructions presented to you.

In a single command, SVN has just performed the following actions for you:

• Get new code
• Delete obsolete code and files
• Replace obsolete code and files with new versions
• Add any new files to the site codebase