Context
The template is inconsistent about the prod environment name:
apps/web/wrangler.jsonc uses env.prod (worker becomes <name>-prod via CLOUDFLARE_ENV: prod)- but
.github/workflows/deploy.yml selects the GitHub environment production (github.ref_name == 'main' && 'production' || 'dev'), and docs/SETUP.md instructs creating dev + production
Surfaced while provisioning a downstream project — dev/production reads as two different naming schemes; dev/prod everywhere is consistent.
Change
.github/workflows/deploy.yml: 'production' → 'prod' in the environment: expressiondocs/SETUP.md: all references to the GitHub production environment → prod (env creation step, secrets/variables tables intro, gh secret set --env production examples, gotcha #5). Convex's own "production deployment" term stays as-is.
Context
The template is inconsistent about the prod environment name:
apps/web/wrangler.jsoncusesenv.prod(worker becomes<name>-prodviaCLOUDFLARE_ENV: prod).github/workflows/deploy.ymlselects the GitHub environmentproduction(github.ref_name == 'main' && 'production' || 'dev'), anddocs/SETUP.mdinstructs creatingdev+productionSurfaced while provisioning a downstream project —
dev/productionreads as two different naming schemes;dev/prodeverywhere is consistent.Change
.github/workflows/deploy.yml:'production'→'prod'in theenvironment:expressiondocs/SETUP.md: all references to the GitHubproductionenvironment →prod(env creation step, secrets/variables tables intro,gh secret set --env productionexamples, gotcha #5). Convex's own "production deployment" term stays as-is.