Copying Drupal database changes to production site?
logicalpat - June 24, 2009 - 17:49
What is the easiest way to copy changes from a development instance of Drupal to a production one?
We've been working on a site update that has many changes in the Drupal database (like new views, new CCK fields, new/updated pages, etc) which would normally be easy to just copy the MySQL database and the Drupal directory over to the production server when we want to go live. However the production instance of Drupal has new content that the development one does not, mostly new blog posts and pages. What's the easiest way to deal with this scenario? I could just manually make the same changes to the production version of the database that I have to the development one but that seems less than ideal. Any input would be appreciated.
i have came across the same
i have came across the same situation many times and haven't found a proper solution. Quite interested to know what others have got to say. Normally either I stall the content update on the production server until port the development server to live or make changes manually. Either way, I feel this is not a good thing.
I have been looking at this
I have been looking at this myself last week... I don't have answers for you, because I've just started reading about this subject, but here are two interesting links:
3. Database Merging (documentation and the discussion of some basic concepts)
Database Scripts (module)