Strategies for version control of a Drupal site project.
Abstract:
Version control with Drupal can be tricky! I can propose and take questions on a way to version control your changes in a popular source control system, like subversion, that even includes database changes.
I'll show how we use module.install files to handle changes, exporting views and cck types and adding them into the .install files and using install profile api to help glue it all together.
I can stretch or shrink this session, change it into a workshop e.t.c. I'll skim over the stuff in here in a separate session over the larger development practice we take at Economist.com.
Length:
20 minutes
(8 votes)
- Ability Level:
- Session Style:
Comments
Not using subversion?
Not using subversion?
I've used subversion to manage database changes to configuration - I didn't need full version control of content
- by using a backup database, clearing out volatile and content tables
then using `mysqldump --skip-opt` and automatically updating subversion with the results.
This does give quite a good history of changes, and can be a good source of SQL to put into update hooks.
This looks like an important session on a sometimes neglected part of the Drupal development cycle.
Sean Burlington
www.practicalweb.co.uk
Post new comment