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) orstaging(aliases:stage,preview,preprod).GMA_TIERandGMA_TARGETare accepted as aliases forGMA_ENV. Default isproduction.GMA_API_URL— overrides the API base URL. Defaults arehttps://api.gitmyabi.com(production) andhttps://api.staging.gitmyabi.com(staging).
OAuth client ids
GMA_GITHUB_CLIENT_ID— override the GitHub OAuth client id used bygma login.GMA_PRODUCTION_GITHUB_CLIENT_ID,GMA_STAGING_GITHUB_CLIENT_ID— tier-specific overrides applied by environment.
Debug and demo
GMA_DEBUG— set to1ortrueto setDEBUG=gma*and print full stack traces.GMA_NO_DEMO— set to1/trueto suppress the first-run demo.GMA_DEMO_FAST— set to1/trueto run the demo at full speed.GMA_DEMO_CHAR_MS— per- character delay in milliseconds for the typewriter effect (default22).CI— when set, the CLI disables the interactive first-run demo.
Publishing
NPM_TOKEN— fallback token used bygma publishandgma generate --publishwhen--tokenand the project config'stokenEnvare 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
- CLI overview
What the gma CLI does and when to use it.
- Sign in with the CLI
Authenticate the gma CLI with your GitMyABI account.
- Publish bindings with the CLI
Use gma publish to upload a bindings tarball to npm.
- CI and GitHub Action
Run gma generate and publish from CI using the official GitHub Action.