env-config

Environment variable management involves centralizing configs in .env files and propagating stage-specific overrides across environments. Define variables in .env.example, then apply environment-specific values to dev/staging/prod by updating corresponding config files in your monorepo apps, ensuring consistent configuration propagation across all deployment stages.

Secrets management separates sensitive data from code by storing API keys, tokens, and database credentials in environment-specific configs rather than version control. Use SST integration to embed secrets securely in serverless stacks, with stage-aware overrides ensuring production credentials remain isolated from development configurations.

SST integration requires embedding environment variables and secrets directly into serverless stack configurations. Propagate stage-specific variables from .env.example through your SST setup, ensuring database connections, API keys, and third-party integrations are correctly provisioned for each deployment environment.

Environment categorization groups variables by function—database, Redis, AI services, workflows, social integrations, build configs, and public variables—enabling clearer management. This organization reduces misconfiguration and makes stage-specific overrides simpler across dev/staging/prod environments in your monorepo.

Variable propagation failures typically occur when .env updates aren't applied to both apps/api and apps/web configurations. Verify that new variables added to .env.example are explicitly set in each app's stage-specific config files and that SST integration is correctly reading environment overrides for your deployment stage.