There are several ways to implement the dev-staging-production but I guess the question here is to create a standard version practice, GIT is good, so is Features, I'm yet to know a way by which I can use them together and come to a point where I can revert to a revision and all my database changes are made accordingly. It has to be something that works with my versioning system. I do not have a solution with me yet, but have been waiting to get time to research/work on the same.<div>
<br></div><div>PS: I've worked with Migraine for dev-staging-production and it works fine for me but I aint very fond of the solution (<a href="http://bit.ly/c4IMUc">http://bit.ly/c4IMUc</a>)<br clear="all"><br>Cheers,<br>
Mukesh<br>
<br><br><div class="gmail_quote">On Sat, May 29, 2010 at 12:45 AM, <span dir="ltr"><<a href="mailto:steve@mirapod.com">steve@mirapod.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 2010-05-28 12:24 , Kevin Davison wrote:<br>
> I'm a proponent of packaging settings into code (out of the DB) with the Features module, along with sharing content changes between development and production (either way) with Deploy and Services. And then you have your settings to check-in to Git repositories for tracking and "easier" deployment.<br>
<br>
</div>i have used Features for configuration; it's got a learning curve, but<br>
one that tends to enforce a discipline, and then you can use your<br>
preference of source control to manage versioned updates to your<br>
configuration; it's a great solution, though it has limitations; you can<br>
use custom modules with install hooks to capture other configuration<br>
that Features can't handle<br>
<br>
i know of Deployment as a solution for content, but haven't used it; i<br>
think managing content is a much harder problem<br>
<br>
[apologies if my reply from a different address also comes through; from<br>
past experience, i'm assuming that mailserver is on a blacklist]<br>
<div><div></div><div class="h5">--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</div></div></blockquote></div><br></div>