Docs

Configuration

Configuration highlights; full details live in source CONFIGURATION.md.

Approving server configuration is primarily YAML / environment variables (local examples: server/config.example.yaml and the root .env.example).

Full documentation

Treat the in-repo docs as authoritative (avoids drift between this site and source):

That document is generated/checked by go run ./cmd/gen-configdoc; CI runs -check.

Local quick path

./start.sh -d          # published image stack
./start.sh dev -d      # source + HMR

Image tags / digests, gateway, and sandbox-related variables are in .env.example. Agent API keys, GITHUB_* / GITLAB_* / SSH, and similar belong in agent meta env (values may reference ${vars.<name>}).

Database and attachment lifecycle

In the release stack, SQLite (./.localdata/db) and app-data / default blobs (./.localdata/app-data, or a custom APPROVING_BLOBS_ROOT) must be backed up and cleaned as a pair; do not migrate only the database. Otherwise composite images can keep orphan blob: refs (GET /api/blobs/:id → 404). Historical orphans only get a permanent UI placeholder; this delivery does not add an inspection console. See Quick start.

Related