Skip to content
Pipebase

Configuration

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

Required

Section titled “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
  • PIPEBASE_JWT_SECRET — 32-byte hex; signs OAuth-issued JWTs

scripts/init.sh generates all four for you.

Optional

Section titled “Optional”

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

Where to set them

Section titled “Where to set them”
WhereWhen
.env at repo rootLocal dev, docker compose up directly
Coolify Application → Environment VariablesCoolify-managed deploys
Your CI’s secret store + .env templateAnywhere 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.