Runex

Docs

Environment variables

Environment variables are how Runex injects configuration into a running deployment — API keys, database URLs, public app URLs, and feature flags — without committing secrets to Git.

Direct answer

Set environment variables in the Runex dashboard for each deployment (or project surface your account provides). Values are available to the process at runtime. Restart or redeploy after changes so the new values are picked up.

Good practices

  • Never commit secrets to the repository
  • Prefer separate values for staging vs production when you run both
  • Use variables for connection strings to external databases and third-party APIs
  • Keep public client-side keys distinct from server-only secrets when your framework supports that split

Common variables

  • DATABASE_URL — connection string for an external database
  • API_URL / NEXT_PUBLIC_* — public endpoints your frontend calls (framework-dependent)
  • Provider tokens for email, storage, auth, etc.

Related