Home ›
Taking a site standaloneTaking a site standalone
Submitted by Benjamin Melançon on October 3, 2007 - 5:24am
Searched words:
Agaric
Agaric procedure for taking a site that was sharing a Drupal codebase with a bunch of other sites standalone.
Download a new Drupal. http://drupal.org/project/drupal
SVN export the current agaric-sites/5/project-name/trunk/sitename.com directory to replace (and rename as) default.
Check the whole thing in.
We'll continue to call modules from our main repository, because that's so useful and it seems you can override a module in /modules/contributions (that's where Agaric puts them) with a module in /sites/all/modules or /sites/default/modules
Resolution
eh, we'll write this up when/if we need to.
More like this
- Sites-available configuration and symlinking best practices
- An individual site Apache virtualhost definition that works for us
- Agaric move site from test to production (for first time) steps
- CVS update, Piston update, and SVN commit of Drupal core upgrade for deployed site
- Bringing a stressed Drupal site back to its feet


Comments
Post new comment