Skip to content
ravel

Environment variables

CLI

Section titled “CLI”
Variable Effect
RAVEL_LOG_FORMAT Sets the default log format (pretty or json) — same as passing --log-format to any command

A team’s own env vars

Section titled “A team’s own env vars”

A team doesn’t reach into process.env directly. Instead:

  • A plugin.ts declares the names it needs via definePlugin({ env: [...] }) and receives resolved values on ctx.env at call time. See Plugins.
  • A tools.json can declare expected env var names via its own env array, which surfaces as an env-missing or env-undeclared lint warning if the declaration and actual usage don’t match. See Config format.

Local development

Section titled “Local development”

For local runs, values come from a standard .env file chain — which must be gitignored, per a team’s .gitignore (see Agent teams). .env is strictly a local-dev convenience; it has no equivalent in production.

In production

Section titled “In production”

There is no .env file in a deployed worker. Values come from secrets bound on the platform and materialized into the worker at start — see Secrets.

Next

Section titled “Next”