Posted by Jackinloadup on October 5, 2012 at 12:42am
Questions That Will be Covered
- What is Version Control and Why Would I Want To Implement it?
- What Makes Version Control Hard in Drupal?
- How Does Drupal Currently address this issue?
Demonstration time!
Other complimenting ideas
Deployment
Content Deployment
What is Version Control and Why Would I Want To Implement it?
Version control in very simple terms allows you to keep track of changes to a project.
Benefits include but are not limited to:
- Building features without disrupting the live version of a website.
- Reverting unwanted or disruptive features (though there are limits here in drupal)
- Grouping configuration into packages called features that can be used across multiple sites.
What Makes Version Control Hard in Drupal?
Drupal 7 and earlier keep configuration exclusively in the database by default. This makes it difficult if not impossible to track changes and test upgrade paths between site versions. Drupal 8's Configuration Management Initiative works to change this to make it much easier and straight forward to export configuration to manageable files.
How Does Drupal Currently address this issue?
The most widely accepted way to manage configuration in Drupal is with install profiles and drush make.
Install Profiles make