deployment-cicd

Create a workflow file in .github/workflows that checks out code, sets up Node.js with npm caching, then runs lint, test, and build jobs. Add deploy jobs gated on the main branch using environment secrets for tokens.

Use the amondnet/vercel-action step with your VERCEL_TOKEN, VERCEL_ORG_ID, and VERCEL_PROJECT_ID stored as GitHub secrets. Pass vercel-args '--prod' for production deploys on the main branch, or omit it for PR preview deployments.

Blue-green runs two full environments and switches all traffic at once after verification. Canary routes a small percentage of traffic to the new version first, monitors error rates, and gradually increases traffic if healthy.

Use multi-stage builds with a node:20-alpine base, copying only production dependencies and build output into the final stage. Add a .dockerignore excluding node_modules, .git, and env files, and order layers from least to most frequently changed.

Add a pipeline step that runs npx prisma migrate deploy with DATABASE_URL provided from CI secrets. Run migrations before the new application version starts serving traffic so the schema matches the deployed code.

By default workflows trigger on all pushes. Add a paths filter to the on.push block to limit runs to directories like src/**, or use paths-ignore to exclude markdown and docs files.