Richard, Sorry, other than what you've described (dump/reload), there's no good solution. On the Digital Pulp project, we're keeping our complete instance (extensions and Radiant source included) in source control. You might consider something like that going forward, at least for managing your non-database stuff. Unless you can come up with a script to do it, any database content will have to be manually copied/merged.
Sean Richard Hurt wrote: > Let's say I have a Radiant site in production and I like it and it's working > fine. Now, the boss comes along and outlines a bunch of content changes > (images, copy, etc.) but no code changes (extensions, etc.) I obviously > cant build the new content in-place on the production system so I fire up a > development environment and get it all worked out. Now my problem is how do > I get all that stuff from DEV -> PROD? > > My first thought was to dump the DEV database and import it into the PROD > database. The problem with that is I risk overwriting production data (!!) > and that doesn't help me move non-database resources (i.e. > /public/images/*). Is there some sort of freeze/thaw that I can use to > migrate this data? Am I completely missing the mark and everyone else just > develops in production? :) How do you move content around? > > Thanx! > Richard > > P.S. I apologize if I've covered this ground before. I looked through the > archives but couldn't find an answer. > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
