[support] Best version control practices

[Mukesh Agarwal]

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.

PS: I've worked with Migraine for dev-staging-production and it works fine
for me but I aint very fond of the solution (http://bit.ly/c4IMUc)

Cheers,
Mukesh


On Sat, May 29, 2010 at 12:45 AM, <steve at mirapod.com> wrote:

> On 2010-05-28 12:24 , Kevin Davison wrote:
> > 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.
>
> i have used Features for configuration; it's got a learning curve, but
> one that tends to enforce a discipline, and then you can use your
> preference of source control to manage versioned updates to your
> configuration; it's a great solution, though it has limitations; you can
> use custom modules with install hooks to capture other configuration
> that Features can't handle
>
> i know of Deployment as a solution for content, but haven't used it; i
> think managing content is a much harder problem
>
> [apologies if my reply from a different address also comes through; from
> past experience, i'm assuming that mailserver is on a blacklist]
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20100529/c74b712e/attachment.html