Skip to main content

Environment variables

Self-hosted Qodex reads configuration from environment variables at boot. Use your platform’s secret mechanism for production: Docker Compose .env, ECS task secrets, Kubernetes Secrets, AWS Secrets Manager, Vault, Doppler, or another managed store. Do not bake secrets into the image. The boot log reports whether critical variables are present, but it does not print their values.

Required for production

QODECLAW_SECRET_KEY must be at least 32 characters. Rotating it invalidates existing encrypted credentials unless you re-enter or re-encrypt them.

Storage

See Storage backends before choosing local disk for production.

Model provider keys

Project-level BYOK keys can override the platform default for that project.

Model selection

Most deployments leave these unset and use the platform defaults.

Queue and concurrency

Without REDIS_URL, Qodex runs scheduler and agent work in-process. That is fine for smaller deployments.

Authentication and workspace defaults

GitHub App

Set these when using GitHub PR review in a self-hosted deployment:

Microsoft SSO

Email and notifications

Uploads, load runner, and Playwright

Minimal Docker example

Next steps

Single-container deploy

Use the smallest working set of variables.

Docker Compose

Wire these variables into a one-host stack.

Storage backends

Configure local disk, S3, or S3-compatible storage.

Secret management

Understand QODECLAW_SECRET_KEY before production.