#Environments

tsdevstack supports multiple deployment environments. Each environment is completely isolated with its own cloud project/account.

#Specifying the Environment

#CLI Commands

All cloud commands accept the --env flag:

npx tsdevstack infra:deploy --env dev
npx tsdevstack cloud-secrets:push --env prod
npx tsdevstack cloud-secrets:list --env staging

#CI/CD Workflows

All workflows accept an environment input.

Environments are configured in .tsdevstack/ci.json:

{
  "provider": "github",
  "environments": ["dev", "prod"]
}

#Environment Isolation

Each environment must use a separate cloud project/account:

The framework validates credentials and rejects deployments if the same project/account is used for multiple environments.

#Why Separate?

• Security - Production credentials cannot affect dev
• Billing - Clear cost attribution
• IAM - Separate permission boundaries
• Quotas - Environments don't compete for limits
• Certificates - SSL certificates are environment-specific

#Adding a New Environment

1. Create the cloud project/account for the new environment

2. Add credentials:

npx tsdevstack cloud:init --gcp
# Follow prompts to configure credentials for the new environment

3. Update CI configuration:

{
  "provider": "github",
  "environments": ["dev", "staging", "prod"]
}

4. Regenerate workflows:

npx tsdevstack infra:generate-ci

5. Add GitHub secrets for CI (environment name in uppercase):

   • GCP_WIF_STAGING
   • GCP_SA_STAGING
   • GCP_REGION_STAGING

   NPM_TOKEN (if your project uses private npm packages) is the only generated-workflow secret that is not per-environment — add it once globally, no _STAGING / _PROD variant. See Private npm packages.

6. Push secrets:

npx tsdevstack cloud-secrets:push --env staging

7. Deploy:

npx tsdevstack infra:deploy --env staging

#Local Development

Local development does not use environments. It uses:

• .secrets.local.json for secrets
• docker-compose.yml for infrastructure
• Services run natively via npm

npx tsdevstack sync
npm run dev