Working with version control on a Drupal/CMS project

Question

I was wondering how teams that develop sites using Drupal (or any other CMS) integrate version control, subversion, git or similar, into their workflow. You\'d obviously wan

Answer 1

You are correct that this is an issue for Drupal--version control works fine until you turn the site over to your client or open it up to users.

Your question seems like a more specific version of this one, which touched on version control in the Drupal workflow. You may find some answers there that help.

For some projects, I have exported all of the views to code, using that feature of the Views module, and I have one project where all of the blocks have been exported, as well. (Although that was a development exercise and not a customary thing to do with blocks.)

Take a look at the work that Development Seed is doing to work around this problem. They are leading the development of the Context, Features, and Spaces modules that work together to store configuration data in modules (outside of the DB) so that it can be versioned with the code.

There is a Drupal group called Packaging & Deployment for discussing the various solutions that are being developed for this issue.