I am sure some wil debate the "Best", but this is what my company does: http://www.garfieldtech.com/blog/drupal-dev-server On Friday 28 September 2007, Andrew Hankinson wrote:
Hi folks,
I'm in the process of developing a new Drupal site that will be fairly active when it gets up and running. As such, I'm wanting to have a development site ("HEAD") and a production site ("RELEASE"), but I'm at a bit of a loss for how to keep the databases in sync, preserving the changes I make on the development side, but not overwriting any of the content that may have been added on the production side.
I'm sure others have run into this same problem, and so I'm wondering - are there any "best practices" documents out there to show how others have done it?
I'll keep looking, but thought I'd appeal to the collective wisdom in case I miss anything.
Cheers, Andrew
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson