CLI and configuration — Nexis documentation

Use the CLI as the contract

Use dev, build, start, serve, check, analyze, routes, create, generate, doctor, test, and upgrade commands as defined by the installed release.

Version configuration

Keep site origin, feed configuration, redirects, rendering choices, OG configuration, and environment policy in checked configuration rather than scattered route assumptions.

Inspect before deploy

The manifest and generated output are the source of truth for an individual release. CI should run deterministic build and validation commands from a clean workspace.

PRACTICAL LABS

Run this capability.

Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.

Use the CLI as the evidence source

Shell

pnpm exec nexis routes
pnpm exec nexis doctor
pnpm exec nexis build
pnpm exec nexis check --budget
pnpm exec nexis analyze

OUTPUT: The configured project reports discovered routes, diagnostics, output policy, and delivery assets.
BOUNDARY: Use the actual production site origin for metadata tests, not an arbitrary local URL.
PROVE IT: Put the commands in CI and preserve the resulting manifest as a build artifact.

VERIFICATION

Prove the contract.

Run the relevant CLI commands in CI, inspect output artifacts, and test the configured origin rather than a temporary preview host.