After I perform 'svn co' of Acquia Drupal, I want to start customizing my install by adding contributed modules, themes and custom modules under the sites/all directory.
Could someone explain how to structure my subversion repositories so that I can keep my own files in the sites/all directory under version control without losing the ability to update Acquia Drupal via the 'svn up' command?
Posted on June 8, 2009 - 06:48 by jam - Senior Wr....
Watch these videos to see how to install Acquia
Drupal from the Subversion repository and then how simple it is to do
clean and fast updates to your SVN-enabled Drupal website.
More information on installation and use of the Acquia Drupal SVN
repository can be found in Acquia's SVN documentation.
I need to move a site from one server to another at a different domain name, and have done so successfully once before. However, now I'm using the acquia svn to update my site.
Do I have to change anything in the svn files which are now in every drupal directory in order to properly use svn with the site on its new server?--the domain name will change as well.
Posted on April 3, 2009 - 23:49 by Chris Brookins.
As part of our mission to help simplify Drupal adoption, we recently made public the Subversion repository (SVN) for Acquia Drupal. Now you can quickly update your site to the latest release of Acquia Drupal with a single 'svn up' command or use one of the many freely available Subversion GUI clients.
Posted on September 4, 2008 - 06:08 by Alex Urevick-Ac....
Are there any plans to allow users to download Acquia via SVN or CVS? I know that once a site is setup than spokes will take care of updates, but it would be great (especially during such active development) to be able to update our local copies without deleting the old files, downloading the new ones, & unpacking them. It would also help to avoid problems with un-compressing the files (i.e. http://acquia.com/network/node/2708 ).
