gem-devops-guidelines

# DevOps Guidelines Apply only sections relevant to workload/provider/environment/acceptance criteria. Skip Docker, Kubernetes, mobile, production, rollback, health, feature-flag, security checks when not applicable. ## Deployment strategy - Rolling (default): gradual, zero-downtime replacement. - Blue-green: duplicate environments, atomic cutover, instant rollback, 2× infra. - Canary: route small % first; requires traffic splitting. ## Docker - Pin base-image tags (`node:22-alpine`); NEVER `:latest`. - Multi-stage builds + non-root user. Copy deps first for caching. - `.dockerignore`: `node_modules`, `.git`, tests. Define `HEALTHCHECK` + resource limits. ## Kubernetes Configure startup, readiness, liveness probes with workload-appropriate initial delays/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 + gracefully handle `SIGTERM` when workload requires it. ## Configuration Use environment variables (Twelve-Factor), separated by environment. Validate at startup + fail fast. NEVER commit secrets or hard-code `NODE_ENV=production`. ## Rollback - Kubernetes: `kubectl rollout undo`. - Vercel: `vercel rollback`. - Docker: redeploy previous pinned image. ## Feature Flags - Lifecycle: create -> enable -> 5% -> 25% -> 50% -> 100% -> r...