Posted by Anonymous on July 26, 2011 at 1:25pm
Hi
First of all, apologies if this has been asked before... I've search around this group and can't find any duplicates.
I'm getting into Git at the moment and was wondering what strategy people use for database modifications when pulling code to a production server. Obviously, Git is brilliant for the code side of things, however I can't seem to find a good solution to sync up the staging database with production without losing any live data and content.
Any tips and advice would be really appreciated!
James
Comments
Features and Drupal 8
Hi James,
This is certainly a pain point felt by everyone! There is no magic solution, but the good news is that the Drupal 8 Configuration Management Initiative will be directly trying to address this.
In the mean time, many people use Features to get as much configuration as possible out of the database and into code.
Hope that helps,
Erik
Maybe don't start with features
Features is great and useful for many things but it is not really a deployment tool per se and often you just want to push configuration changes while KEEPING the item configuration and not artificially converting it into a code object with features/strongarm.
So my advice is start using hook_update_N hooks in a site module for deploying such changes..