Configuration

Pipebase is configured entirely via environment variables. Set them in .env (or via your orchestrator’s UI — Coolify / Portainer / your CI).

Required

• ROOT_DOMAIN — the domain you serve Pipebase on
• LETSENCRYPT_EMAIL — Let’s Encrypt contact address
• PIPEBASE_DEPLOY_TOKEN — 32-byte hex; bearer token between designer↔runtime

scripts/init.sh generates all three for you.

Optional

• PIPEBASE_JWT_SECRET — opt-in; pins OAuth-issued JWTs and lets the runtime verify flow-level bearer policies. Off in both shipped compose files (commented lines on the designer and runtime services in the standalone file). Trade-off in the environment variables table.

Per-host overrides, runtime URLs, log level, broker URLs — full table at environment variables.

Where to set them

Where	When
.env at repo root	Local dev, docker compose up directly
Coolify Application → Environment Variables	Coolify-managed deploys
Your CI’s secret store + .env template	Anywhere else

docker-compose.yml interpolates from .env by default. Required vars use the ${VAR:?VAR must be set} form so Compose fails loudly if they’re missing — no silent boot-with-empty-token surprises.