Skip to main content
Every Meteroid process is configured with environment variables. The Docker Compose file and the Helm chart set most of them for you; this page lists them all, per process, so you can tell what you must provide and what you can tune.
  • Required: the process does not start without it.
  • Recommended: it has a default, but the default is rarely right for a real installation.
  • Optional: the default suits most installations.
The API and the worker read the same configuration, and refuse to start when a required variable is missing or a value is invalid. Set the same variables on both, even those only one of them acts on. Booleans are true or false. Schedules are cron expressions with five fields, evaluated in UTC.

API and worker

Required

SECRETS_CRYPT_KEY must be exactly 32 characters, or the process refuses to start. It defaults to 32 zeros, which encrypts nothing worth the name: set your own before the first start, for example with openssl rand -hex 16, and never change it. It encrypts the credentials of your payment, accounting and CRM connectors: with another key, Meteroid can no longer read them and every connector must be set up again. Back it up with your database backups.

Optional

Email Object storage Accounts and organizations Outgoing webhooks Database pool API only API rate limits (Enterprise images, with REDIS_URL set) The REST limits each have a value for Production tenants and one for the other tenants, and are counted per tenant, except the client routes, counted per customer. Worker only Instance bootstrap (API) On a fresh installation, the API can create a first user, organization, tenant and API key at startup, for scripted installs and CI. On an installation that already has an organization, it stands down. Re-running it converges on the same objects. Telemetry

Enterprise images only

The open-source edition does not read these.

Metering API

Required

Optional

Web

The web image writes these into the app when the container starts, so one image works on any domain.

Helm values

The Helm chart sets these variables from its values (for example global.publicRestApiUrl for METEROID_REST_API_EXTERNAL_URL, and the listen addresses and internal URLs by itself). For a variable the chart does not map, use the component’s extraEnv. See Deploy on Kubernetes.