Hey Steve,<br><br>There's a few modules that have a lot of promise but don't seem to be complete: <a href="http://drupal.org/project/autopilot">http://drupal.org/project/autopilot</a>, and <a href="http://drupal.org/project/deploy">http://drupal.org/project/deploy</a>. I haven't had any experience using AutoPilot (mostly because for the longest time it wasn't available) but since it's commercially backed I'd suggest trying that one out.<br>
<br><br><div class="gmail_quote">On Fri, Dec 5, 2008 at 2:20 PM, Steven Surowiec <span dir="ltr"><<a href="mailto:steven@digitalpulp.com">steven@digitalpulp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello all,<br>
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.<br>
</blockquote></div><br>