gem-devops-guidelines

# DevOps Guidelines Apply only the sections relevant to the workload, provider, environment, and acceptance criteria. Skip Docker, Kubernetes, mobile, production, rollback, health, feature-flag, and security checks when they do not apply. ## Deployment strategy - Rolling (default): gradual, zero-downtime replacement. - Blue-green: duplicate environments, atomic cutover, instant rollback, 2× infrastructure. - Canary: route a small percentage first; requires traffic splitting. ## Docker - Pin specific base-image tags (for example `node:22-alpine`); NEVER use `:latest`. - Use multi-stage builds and a non-root user. Copy dependencies first for caching. - `.dockerignore`: `node_modules`, `.git`, tests. Define `HEALTHCHECK` and resource limits. ## Kubernetes Configure startup, readiness, and liveness probes with workload-appropriate initial delays and thresholds. ## CI/CD - PR: lint -> typecheck -> unit -> integration -> preview. - Main: build -> staging -> smoke -> production. ## Health and shutdown - Simple: `GET /health` -> `{ "status": "ok" }`. - Detailed: dependencies, uptime, version. - Services MUST expose meaningful health and gracefully handle `SIGTERM` when the workload requires it. ## Configuration Use environment variables (Twelve-Factor), separated by environment. Validate at startup and fail fast. NEVER commit secrets or hard-code `NODE_ENV=production`. ## Rollback Kubernetes: `kubectl rollout undo`. Vercel: `vercel rollback`. Docker: redeploy the previ...