We're trying to put together a workflow for Wordpress development which turns out to be pretty complicated with lots of elements. Is there a way to streamline this or filling in the gaps?We currently have 2 developers in the team - but essentially this can be however many, all working in the same way.The problemsWP Stagecoach seems the only way to allow us to merge a database rather than just copying over one. Does anyone know any other methods?We work on a lot of sites that need the live version to continue to run (and the data get updated)... whilst developing new features (therefore both versions are adding to the posts table in the database). This brings up the problem of losing data, copying over some etc etc.The problem Wp Stagecoach has is that we can create a staging site, make the changes there, then merge back with the live site - that part works great. But we want to be able to work locally rather than on a staging site (which HAS to be on the Stagecoach servers).So the real question is, how can we work on a site locally, and get it live without copying over live data (i.e merging with it)? Doing the files is straightforward, it's the database that causes the problem.
Development workflow for a team: local to live (with GIT)
git;teamwork;workflows;wordpress