[support] Best version control practices

[Kevin Davison]

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.

However, each project needs its own customized plan, and there's currently no ultimate method. It's also going to take time for the DB vs. Code argument to resolve in the Drupal community. Drupal 8 or 9?

On May 28, 2010, at 08:02 AM, Rolf Kutz wrote:

> On 28/05/10 09:50 -0400, Ari Davidow wrote:
>> 
>> Yes, that is a beautiful explanation of git. I am still trying to
>> think about the best way to deal with drupal configuration issues, to
>> note module dependencies, and to deal with the fact that in a cms
>> database, because of all of the auto-numbering dependencies, we have a
>> model where we have successfully merged content and code--exactly
>> where we didn't mean to be ;-). This may all clarify as I move
>> forward.
> 
> I haven't found a perfect solution for that, yet,
> especially for the problem of switching between
> production and development version on a
> development server. Syncing the configuration (aka
> the database) between the two is kind of lossy, so
> you end up using two different installations and
> databases. This should be simple to manage with
> git.
> 
> regards
> Rolf
> -- 
> ... Expediency asks the question, 'Is it politic?' ...
> -- 
> [ Drupal support list | http://lists.drupal.org/ ]