Is there a testing environment with separate database or should we clone the app for production releases? How do you make sure the databases are persistent between releases if this is done?
With the cloning approach (which is great, by the way), be careful as you make development changes to note any data table changes you make. You’ll have to make those again in the production clone, as there isn’t any automated way to propagate those changes.
I have some additional steps I’ve found needed in a couple of threads: Data Tables & Git Repos and Cloning apps and data tables for Production and Development Apps
There are some gotchas in those that weren’t obvious to me, but became necessary during the initial cloning of a production version of the app.
3 Likes