Reference
Where to find every command and flag, every configuration file and key, the template API for your project, environment variables, exit codes and error codes, and how to get the same from the binary.
The reference lists everything exactly: every command, every configuration key, every exit and error code. The other sections explain how and why; come here for the precise name, type, default or limit.
From the binary
The binary describes itself, and what it prints always matches the version you run:
| To get | Run |
|---|---|
| Every command, argument and flag, as JSON | engine-dmo help --json |
| One command’s flags | engine-dmo <command> --help |
| The JSON Schema of every configuration file | engine-dmo config schema --json |
The resolved engine.yaml with every default | engine-dmo config render |
| Every field type and its parameters | engine-dmo describe fieldtypes --json |
| The template surface of your project | engine-dmo template api --json |
| Your project’s sites, types, routes and the rest, with ids | engine-dmo describe project --json |
| Version, bundle, modules and capabilities | engine-dmo version --json |
| This handbook as Markdown | https://docs.cherwell.studio/llms.txt, https://docs.cherwell.studio/llms-full.txt |
Scaling
Running more than one engine replica behind a load balancer, covering what each replica does, the scheduler lease, shared storage, caches across replicas, background job workers, database connections and the page cache.
CLI
Every engine-dmo and engine-cms command by purpose, the global flags, --json output (data or envelope), --quiet, how a command finds its project, and how to list the whole command tree as JSON.