[development] Multi-instance Drupal Deployment

[Sam Boyer]

There's also the Drupal Automated Staging Toolkit (DAST - 
http://drupal.org/project/DAST), which is Phing-based, and so might relieve 
the need for you to continue putting time in on developing something with 
Phing.

On Friday 05 December 2008 14:20:11 Steven Surowiec wrote:
> Hello all,
>     I've using Drupal at lot at work lately and have some pretty big
> Drupal projects coming up and have been facing the same problem with all
> of the previous projects that I would like to get worked out before
> these new ones get going. And that is handling Drupal deployment in a
> multi-instance environment (multiple developers with local installs, a
> singular development server, a staging server and the production
> server). I can, and currently am, setting up Phing to do most of the
> work for me of handling SVN during the deploys and running any custom
> scripts. But the big hurdle is the database. Particularly the fact that
> there's a lot of admin-editable settings that are stored in various
> database tables. I was wondering if anyone else has had to deal with
> this before and any insight into the problem would help.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.drupal.org/pipermail/development/attachments/20081205/c74ecaf5/attachment.pgp