gtmesh render-manifest
Emits the set of slugs that should render for a given environment.
gtmesh render-manifest --env <env> [--out <file>]What it does
Not every catalogued page renders in every environment. gtmesh render-manifest resolves your registry and environment rules into the concrete list of slugs that should be built for one environment — local, dev, prod, or whatever you’ve configured — and writes that manifest to disk.
Your site’s build step reads the manifest to know exactly which pages to render, so the renderable set is decided deterministically by the engine rather than guessed at build time. It’s the same set gtmesh status --env <env> shows; this command writes it to a file.
--env is required — a manifest only means something for a specific environment.
Arguments & flags
| Option | Description | Default |
|---|---|---|
--env <env> | Required. Environment to emit the set for (e.g. local, dev, prod) | — |
--out <file> | Override the manifest output path | the configured default path |
The global options (--project, --json, --quiet) also apply.
Reads & writes
- Consumes: the committed registry and the environment’s render rules.
- Produces: the manifest file — the renderable slug set for
--env. - Commits: typically the manifest is a build artifact your SSG consumes; commit it or regenerate it in CI per your workflow.
Examples
gtmesh render-manifest --env prod
gtmesh render-manifest --env dev --out build/dev-manifest.jsonRelated
status— see the same render set inline (--env).- Lifecycle & reconcile — what
publishedand the other statuses mean. - Reference — the version-exact flag list.