BWEZE Docs

Environment variables

Configure a service with variables, encrypted at rest and frozen with each release.

Apps need configuration - a database URL, an API key. Add it as environment variables, one KEY=VALUE per line: on the Deploy form under Environment variables, and later on the project's Environment variables page:

DATABASE_URL=postgres://…
STRIPE_SECRET_KEY=…

When they apply

  • Variables are available at build time and at runtime: a Dockerfile build sees them as build arguments, a Railpack build as build secrets.
  • Each release freezes a snapshot of the variables it was built with. A change applies from the next deploy, so Redeploy after editing. A rollback brings back the old release's variables too.
  • Jobs and pre-deploy commands get the same variables as the release they run on.

How they are kept

Every value is encrypted with its own AES-256-GCM key, which is itself encrypted under a key-encryption key that never leaves BWEZE's control plane. Values travel to the cluster sealed for it (X25519, HKDF-SHA256, AES-256-GCM) and are only opened there.

Limits

  • At most 200 variables per service.
  • Names starting with KUBERNETES_ or BWEZE_AGENT_ are reserved.
  • PORT sets the port a web or private service listens on (see Services).

On this page