Skip to main content


Anyone have suggestions for workflow developing a site with a database-driven CMS? (#Wordpress but I’ve wrestled with the same question regarding #Drupal and other systems.) #Git seems necessary but insufficient because rolling back code after schema changes have been made can mess stuff up. There are a lot of references online but few address this question and I haven’t yet seen one that addresses it well. I’ve been doing this 28 years now and workflow still perplexes me.
@evan Thank you! I should have written "rolling back code after any change has been made to or in the database", not just schema changes.

Just thinking out loud here: maybe I should make a dump of the entire database and let that sit in a directory above docroot, and just check that into git. I mean, it's code. Minimal changes mean minimal storage requirements.

I'm starting to get the sense that there's a reason why large projects hire people that are smarter than me.
so, look into a schema migration tool and try it.