Configuration

A project’s configuration is YAML under config/ (or the directory --config names). It is committed to git: secrets never appear in it, only ${VAR} interpolations. Every file is checked as a whole, and every problem is reported together, each with its file, line and column, the source line and a caret.

engine-dmo check --no-db               # every file, with no database
engine-dmo config validate             # engine.yaml alone
engine-dmo config render               # engine.yaml resolved, defaults included, secrets redacted
engine-dmo config schema --file site   # one file's JSON Schema

The filesCopy Anchor Link

A new project from engine-dmo init has engine.yaml, locales.yaml, access/grants.yaml and one site’s site.yaml and routes.yaml; every other file is optional. A file for a module the binary does not compile (such as memberships.yaml under engine-cms) is refused by the module’s name.

Stable idsCopy Anchor Link

Elements that hold data (types, fields, groups, blocks, options, sites, locales, routes, endpoints, tiers, networks, screens, actions, roles, slots and landing families) carry an id, such as fld_thsh2xa6nf. The id is what stored data is keyed by, so renaming a handle keeps its data. Never write or change an id by hand:

engine-dmo check --fix --no-db    # writes every missing id in place, keeping comments, then checks

check without --fix reports a missing id as an error. The engine-dmo dev authoring verbs write ids as they add elements. See Stable ids.

Shared value formatsCopy Anchor Link

Editor supportCopy Anchor Link

engine-dmo init writes the JSON Schema of every file to .meridian/schema/ and maps the file patterns to them in the project’s VS Code and Zed settings. To refresh them after an engine upgrade:

engine-dmo config schema --write .meridian/schema --editors vscode,zed

Each schema is generated from the structures the loaders decode, so an editor’s completion and validation match what check accepts.