When Syncing Servers Gives You Headaches

Matt and I (Jen) have been banging our heads against the wall nearly continuously for the last week.

We’re trying to figure out how the workflow works (heh!) when you’ve got a website that is both live (on the internet, open to the public) and in development (on our computers) at the same time.

We’ve had this problem for quite a while, really, but now it’s coming to a point. Matt’s been working on a big project for a big client that already has a website.

We have one copy of their database here on our server that holds everything we’ve been working on recently. We have another copy of their database connected up to the live website that holds quick fixes and updates to pages that hadn’t quite made it back to our local copy.

If we use our local copy and overwrite the live site, then we lose everything that’s been added in the last few months. If we update our local copy with what’s on the live site, we overwrite a bunch of the posts that Matt’s been working on locally over the last few months.

The tools and apps we can find that try to alleviate this problem seem to really just not work. Most will overwrite conflicting content without asking. Even WP Exporter will only let you export big blocks of custom post types, not allowing any cherry-picking of particular posts.

Anybody else have this particular problem? We’d love to hear a solution that makes sense.

This entry was posted in Web, Workflow. Bookmark the permalink.

Leave a Reply