Hello,
I ’m looking for recommendations / best practices to migrate a full Compose “release” from DEV to PROD.
Today, it’s straightforward to move:
-Modules (export/import),
-Workflows(export/import),
-Charts(export/import),
…but I’m struggling with (Page Builder / Compose Pages). I don’t see an equivalent export/import workflow for Pages the way we have for modules/workflows/charts.
My use case is: I want to deploy a consistent upgrade package that includes “modules + workflows + charts + pages” , where pages reference the modules/fields and embed workflow-driven blocks and charts. In other words, I need a repeatable DEV → PROD promotion process, not manual page rebuilding every time.
Questions:
- What is the recommended approach to migrate between environments?
- Is there an official export/import for pages (or a supported API / CLI / provisioning approach) that I should use?
- If the only option is via DB-level migration, how do you handle it safely (IDs, references, environment differences, rollbacks)?
- Any patterns to keep pages stable across environments (handling module IDs/field IDs, avoiding broken references)?
- If you’re doing this in CI/CD, what does your pipeline look like?
Context: I’m on Corteza 2024.9.6, running on Docker + PostgreSQL. I’m aiming for a clean and reliable promotion process across DEV / staging / production.
Thanks a lot for any guidance or examples from real deployments.