[consulting] New project drupal workflow

[Troy Arnold]

On Fri, Mar 06, 2009 at 11:30:24PM +0100, George wrote:
> I'm testing the idea of having a local repos of drupal and the essential 
> module (and some not so essential modules) and checking out when i start 
> a new drupal project, and installing. of course this has the negative 
> that modules and drupal slowly fall out of date, but i find it 
> incredibly quick just to checkout, and start with the all the modules, 
> and take away what i don't want.

It sounds to me like a pretty terrible idea to start with something that is
already out of date.  If you want a rapid start, why not just run multiple
sites out of one Drupal install?

Also the drush module is pretty darn spiffy for quick module installs.

> i'm thinking about combining this with an install profile to 
> automatiically enable the core essential modules cck / views etc to 
> remove an extra layer of module enabling!

> do any of you do anything similar? or do you have a different system?

I have a Drupal project that periodically needs to get cloned into a new
instance.  I ended up writing a Perl script to handle the tedious parts of
cloning the database, copying over and resources, erasing the un-needed
content and writing a new settings.php.  That's probably a raunchy hack,
but it was easier (for me) than learning the install profile system.  It
does require that you understand Drupal's database schema very well.

It's a slightly different question than what you're asking, but for
maintaining Drupal sites with a minimum of hassle I use a method largely
based on David Grant's writeup:
<http://www.davidgrant.ca/maintaining_vendor_sources_with_subversion>

-t