Meridian handbook
ReferenceCLI

render

engine-dmo render: Render a public page through the real pipeline, in process; --json adds errors, queries, assets, accessibility findings and the image report. Every subcommand, argument and flag.

Render a public page through the real pipeline, in process; --json adds errors, queries, assets, accessibility findings and the image report.

engine-dmo render <path> [flags]
ArgumentRequiredRepeatable
pathyesno
FlagTypeDefaultMeaning
--fragmentstringrender only these fragments of the page, comma separated, as a script’s request for them gets them
--hoststringthe Host the request carries (default: the site’s first domain, or the locale’s under the domain strategy)
--localestringlocale code; the path is then the unprefixed URI and the locale’s prefix or domain is added
--sitestringsite key (default: the default site)

--json prints the command’s own JSON document. Runs in a project.

render boots the engine in process, so it needs a reachable database and every variable the configuration names. It prints the engine’s start-up log lines to standard error before the page; when the database cannot be reached it prints those lines, then the error (MRD-3001), and exits 1. Read the exit code, not the first line of output. With no database there is no way to render a page; check with --no-db is the furthest a project can be verified.

Under render, csrfToken(), csrfInput() and the csrf global print empty, because no request key exists outside a running server. A form is complete only when served by engine-dmo serve.