LanguageGB
App Deployment

Environment variables

Environment variables should be planned without exposing secrets.

What this means

What this means

Apps often need configuration values such as API URLs, database connection names, feature flags, and secret references.

Before you start

Before you start

List required variable names, which values are secret, and which environment each value belongs to.

Step-by-step guidance

Step-by-step guidance

  1. Separate public config from secret values.
  2. Never paste passwords or private keys into public notes.
  3. Document variable names and purpose.
  4. Confirm who will provide production secrets through a safe channel.

What CM Cloud support will review

What CM Cloud support will review

Support reviews required variable names, secret handling path, runtime needs, and whether any value affects billing or providers.

What is not automated yet

What is not automated yet

This guide does not store secrets, create environments, deploy apps, or call providers.

Safety note

Safety note

Reading this article does not trigger payment, provisioning, DNS, registrar, Cloudflare, WHMCS, or provider actions.

Safe next action

Safe next action

Prepare a redacted variable list and ask support for the safe submission path.

Contact Support