Skip to main content
bap-engine’s settings are loaded from environment variables prefixed ORCH_* (Pydantic BaseSettings). LLM provider keys (LLM_API_KEY, OPENAI_API_KEY, etc.) aren’t ORCH_-prefixed because they’re forwarded to engine containers; the orchestrator just passes them through.

Required

Engine provider keys (passed through)

The orchestrator forwards these to engine containers — it doesn’t read them itself. Engines need them to talk to LLM providers. These are forwarded only if listed in ORCH_ENGINE_ENV_PASSTHROUGH.

Orchestrator configuration

Health and recovery

See Health and auto-restart for tuning by use case.

Build-time only

Conventions

  • Booleans are not used in orchestrator settings — most knobs are ints or strings. The engine’s "true" / "false" convention applies to engine vars, which the orchestrator forwards as-is.
  • Paths are absolute when crossing the orchestrator-to-Docker boundary; relative paths get resolved against the orchestrator’s working directory.
  • Secrets never go in code or images. Inject from your secret manager at runtime.

Local-dev shortcut

For the local quickstart, this minimal .env works:
See Quickstart for the full walk-through.

See also

  • Architecture — what each var affects.
  • Deploy — production setup.
  • HealthORCH_HEALTH_* and ORCH_RESTART_* tuning.
  • SecurityORCH_MASTER_KEY rotation.