We’re going live with our prod site soon, and I’m trying to establish a nice dev migration pathway so we build and test on a dev server, then deploy reliably to prod. In particular, I’m concerned about migrating the page layouts we build that are stored in the database.
I can export/import the vocabularies, SKOS thesaurus, and Resource Templates, but I can’t find an option for doing the same for settings for Sites, Pages, Navigation, Theme, etc. I don’t want to manually recreate every setting and page, that would take forever and be prone to error. I guess I could do a custom SQL script to export from dev?
How do others deal with this? Any suggestions? Am I just missing something really obvious?
Thanks John, unfortunately there will be a fairly steady addition of new data to the prod site while we actively add new features in dev, so trying to keep the two in sync would be problematic. I’d also be generating test data in dev that I wouldn’t want to copy to prod.
I suspect I’ll hack up something to export/import just the site config tables and step carefully around the item/item set relations.
We struggle with this too. One thing we’ve tried is importing the content from prod to dev via api before remigrating/upgrading new features etc back the other way. Keeping dev test data in a test set or site makes it easy to hide or remove afterwards on prod.
What I’m now thinking is adapting wragge’s python library to migrate sites. It can already migrate resource templates, so surely it can’t take much to migrate sites and pages as well (famous last words…)? That’s assuming the API allows to modify the sites and pages and isn’t just read-only?