Environment variables

Environment variables the gma CLI reads.

CLI

Variables are read at process start. CLI flags, when present, take precedence over these.

Environment selection

  • GMA_ENV — selects the target deployment. Values: production (aliases: prod, live) or staging (aliases: stage, preview, preprod). GMA_TIER and GMA_TARGET are accepted as aliases for GMA_ENV. Default is production.
  • GMA_API_URL — overrides the API base URL. Defaults are https://api.gitmyabi.com (production) and https://api.staging.gitmyabi.com (staging).

OAuth client ids

  • GMA_GITHUB_CLIENT_ID — override the GitHub OAuth client id used by gma login.
  • GMA_PRODUCTION_GITHUB_CLIENT_ID, GMA_STAGING_GITHUB_CLIENT_ID — tier-specific overrides applied by environment.

Debug and demo

  • GMA_DEBUG — set to 1 or true to set DEBUG=gma* and print full stack traces.
  • GMA_NO_DEMO — set to 1/true to suppress the first-run demo.
  • GMA_DEMO_FAST — set to 1/true to run the demo at full speed.
  • GMA_DEMO_CHAR_MS — per- character delay in milliseconds for the typewriter effect (default 22).
  • CI — when set, the CLI disables the interactive first-run demo.

Publishing

  • NPM_TOKEN — fallback token used by gma publish and gma generate --publish when --token and the project config's tokenEnv are not set.

You can also point the CLI at a custom env variable by setting tokenEnv in gma.config.json; the init template uses NPM_TOKEN.

Other

  • GMA_GH_INSTALL_URL — override the GitHub App install URL surfaced in project setup flows.

Related