Environment variables

Variables doze reads

Variable	Effect
DOZE_HOME	The shared home (default ~/.doze): engine cache, module cache, per-project state.
DOZE_VAR_<name>	Sets config variable "<name>" (lower precedence than --var).
DOZE_MODULES	off disables module fetching entirely (offline / process-only).
DOZE_MODULES_MIRROR	Registry base override — URL or file:// path.
DOZE_<TYPE>_PLUGIN	Path to a local plugin binary for an engine type; skips registry fetch and its metadata gates (module development).
DOZE_<ENGINE>_BINDIR	Explicit engine bin directory (e.g. DOZE_POSTGRES_BINDIR); bypasses mirror + lock.
DOZE_<ENGINE>_MIRROR	Per-engine binaries-mirror base.
DOZE_MIRROR	Global binaries-mirror root (engine name appended).
NO_COLOR	Plain output (also automatic when stdout isn’t a terminal).

Precedence, where they overlap: explicit local override (_PLUGIN/_BINDIR) → lockfile pin → mirror/registry resolution.

Variables doze writes (for process blocks)

A supervised process receives connection variables for the dependencies it references — the same set written to .doze/endpoints.yaml for external tooling (doze run deliberately does not inject them; see Workflows):

Variable	For
DATABASE_URL	postgres
REDIS_URL	valkey / kvrocks
MONGODB_URI	ferret
MYSQL_URL	mariadb
AWS_ENDPOINT_URL_S3 / _SQS / _SNS	the local AWS engines
AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY / AWS_REGION	dummy credentials the local AWS engines accept (test / test / us-east-1)

Per-instance attributes (postgres.app.url, sqs.jobs.name, …) are also available as config references for wiring values explicitly.