Posted by logicalpat on June 24, 2009 at 5:49pm
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.
Comments
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)
I have the same situation.
I have the same situation. I've uploaded a demo site for my client and he has added new nodes menus and taxonomy, now I need to know what exactly these tables are in database so I can override or sth.
any1 has ever done this before?
Pooya Sanooei
My Main Problem With Drupal
I use Drupal for my own sites, but I cannot honestly recommend it to my clients. Upgrading is an unmanageable process.
Best regards,
Bill
I understand why you're not
I understand why you're not fond of the upgrade process, but I wouldn't call it an unmanageable process. It must be said that a lot has changed since this forum topic started two years ago (exportables, features), and Drupal is definitely heading in the right direction with this.
Unfortunately I spend more time configuring and fixing Drupal.
Unfortunately I spend more time configuring and fixing Drupal than I do managing the content on my sites. My latest is GroupPoopOn.com. I first used the Titan theme. Then I switched to Pixtures Reloaded because it gave me more configuration control. I liked it, worked great. I figured out the Colors module quirk where it creates a new folder with new CSS files every time you save it, I think. I spent a month tweeking the presentation layer (CSS).
Then I upgraded to the latest Drupal version and after spending a day or two getting stuff running, the world was good. Unfortunately, I didn't save my web and database at that point in time.
I noticed my favicon wasn't right, so, I went into the Pixtures Reloaded appearance settings and changed my favicon. POW, now my site is some freaking green theme, even though my "colors" settings are what they are supposed to be. Imagine that! Change your freakin favicon and it blows your site away!
And I'm back to the Titan theme and had to change update all the structure/block settings, etc. And of course I had to do it over the Internet on an Amazon AWS virtual server, because I can't do the changes locally and then deploy them in a controlled manner.
I'll figure this out, because that is what I do. And sorry, my rant is really a cry for help. I'll pay handsomely for a Drupal consultant who can give me a deployment methodology that works.
Did I mention I spend more time configuring and fixing Drupal than I do managing the content on my sites?
Best regards,
Bill
Bill, I see your frustration.
Bill, I see your frustration. I'm not the consultant you're looking for, but there must be people out there who can help you getting it right.
Still reevaluating.
I'm still reevaluating whether or not I want to continue moving forward. I've been working with Drupal for over a year now, and sometimes the most simplistic changes (like changing my favicon) have a disasterous effect. Hey, all environments are going to have their quirks, but the problem is magnified by the fact there are no typical SDLC capabilities. I like having a development environment, a staging environment and a production environment. I think that is the real problem - Drupal is not conducive to having that environment.
Once a major snafu happens, in many cases you have to revert back - and that just doesn't cut it on an active production site.
That being said, I like the theming architecture and the ability to over-ride code without touching the core.
Best regards,
Bill