Expand description
Embed + materialize the bundled CMS migrations.
rustango-cms ships its own per-tenant schema (cms_page,
cms_page_type, cms_locale, cms_media, …) as JSON migration files
under migrations/. Downstream apps need those migrations applied
against every active tenant, but they live inside the library
crate — not the user’s project — so the manage CLI’s
migration-runner has nowhere to find them by default.
Solution: rustango::embed_migrations! bakes the JSON into the
library at compile time as &'static [(name, json)]. The
materialize helper writes any missing entries into the user
project’s migrations/ dir on first boot. Idempotent — existing
files (with matching names) are left alone, so user customizations
are not clobbered.
§Wiring
ⓘ
use rustango::manage::Cli;
#[rustango::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let migrations_dir = std::path::Path::new(env!("CARGO_MANIFEST_DIR"))
.join("migrations");
// Materialize CMS-bundled migrations before the runner reads
// the directory. Safe to call on every boot.
rustango_cms::migrations::materialize(&migrations_dir)?;
Cli::new()
.tenancy()
.migrations_dir(migrations_dir)
/* … */
.run().await
}Constants§
- MIGRATIONS
- The CMS migrations embedded at compile time. One entry per JSON
file in
rustango-cms/migrations/. The macro also performs static chain validation — a brokenprevreference fails the build rather than the runner.
Functions§
- materialize
- Write every embedded CMS migration into
target_dirif a file with the matching name doesn’t already exist. Idempotent — safe to call on every boot. Existing files are not overwritten so user edits / squashed-migration overrides survive.