Timeline for How do I merge changes from a development copy of the site to the live site without losing new content?
Current License: CC BY-SA 2.5
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 3, 2011 at 19:51 | comment | added | coderintherye | In option 1, we now use node_export to regularly send over the content (having removed previous content). We used to make content changes on both dev and prod. This is actually a common scenario at a few places I've seen, though obviously not ideal. This is why I add, adopt a direction and stick with it, either content goes dev -> prod or prod -> dev, but try not to do both. And yes, we basically overwrite, although more like erase and rebuild. At my new job we do #2, at my old job we did #1 but are moving to #2 (im still consulting for them). | |
| Mar 3, 2011 at 1:01 | comment | added | Chaulky | In option 1, how are you recreating the content that has been added to the live site that isn't in the dev site? It seems like you're overwriting all of it with the dev db and then maybe changing some settings/variables. Also, which school of thought are you using on your sites currently? Any pros and cons to each approach? | |
| Mar 3, 2011 at 0:54 | history | answered | coderintherye | CC BY-SA 2.5 |