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 Prodromou
•the management of incremental, reversible changes and version control to relational database schemas
Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)Steve Scotten
•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.
Evan Prodromou
•