[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72Y1T20DAHZ65202Q8KPKB8":3,"skill-same:01M72Y1T20DAHZ65202Q8KPKB8":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M72Y1T20DAHZ65202Q8KPKB8","deployment-patterns",null,"部署工作流、CI\u002FCD流水线模式、Docker容器化、健康检查、回滚策略以及Web应用程序的生产就绪检查清单。","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fdeployment-patterns\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: deployment-patterns\ndescription: 部署工作流、CI\u002FCD流水线模式、Docker容器化、健康检查、回滚策略以及Web应用程序的生产就绪检查清单。\norigin: ECC\n---\n\n# 部署模式\n\n生产环境部署工作流和 CI\u002FCD 最佳实践。\n\n## 何时启用\n\n* 设置 CI\u002FCD 流水线时\n* 将应用容器化（Docker）时\n* 规划部署策略（蓝绿、金丝雀、滚动）时\n* 实现健康检查和就绪探针时\n* 准备生产发布时\n* 配置环境特定设置时\n\n## 部署策略\n\n### 滚动部署（默认）\n\n逐步替换实例——在发布过程中，新旧版本同时运行。\n\n```\n实例 1: v1 → v2  (首次更新)\n实例 2: v1        (仍在运行 v1)\n实例 3: v1        (仍在运行 v1)\n\n实例 1: v2\n实例 2: v1 → v2  (第二次更新)\n实例 3: v1\n\n实例 1: v2\n实例 2: v2\n实例 3: v1 → v2  (最后更新)\n```\n\n**优点：** 零停机时间，渐进式发布\n**缺点：** 两个版本同时运行——需要向后兼容的更改\n**适用场景：** 标准部署，向后兼容的更改\n\n### 蓝绿部署\n\n运行两个相同的环境。原子化地切换流量。\n\n```\nBlue  (v1) ← 流量\nGreen (v2)   空闲，运行新版本\n\n# 验证后：\nBlue  (v1)   空闲（转为备用状态）\nGreen (v2) ← 流量\n```\n\n**优点：** 即时回滚（切换回蓝色环境），切换干净利落\n**缺点：** 部署期间需要双倍的基础设施\n**适用场景：** 关键服务，对问题零容忍\n\n### 金丝雀部署\n\n首先将一小部分流量路由到新版本。\n\n```\nv1：95% 的流量\nv2：5% 的流量（金丝雀）\n\n# 如果指标表现良好：\nv1：50% 的流量\nv2：50% 的流量\n\n# 最终：\nv2：100% 的流量\n```\n\n**优点：** 在全量发布前，通过真实流量发现问题\n**缺点：** 需要流量分割基础设施和监控\n**适用场景：** 高流量服务，风险性更改，功能标志\n\n## Docker\n\n### 多阶段 Dockerfile (Node.js)\n\n```dockerfile\n# Stage 1: Install dependencies\nFROM node:22-alpine AS deps\nWORKDIR \u002Fapp\nCOPY package.json package-lock.json .\u002F\nRUN npm ci --production=false\n\n# Stage 2: Build\nFROM node:22-alpine AS builder\nWORKDIR \u002Fapp\nCOPY --from=deps \u002Fapp\u002Fnode_modules .\u002Fnode_modules\nCOPY . .\nRUN npm run build\nRUN npm prune --production\n\n# Stage 3: Production image\nFROM node:22-alpine AS runner\nWORKDIR \u002Fapp\n\nRUN addgroup -g 1001 -S appgroup && adduser -S appuser -u 1001\nUSER appuser\n\nCOPY --from=builder --chown=appuser:appgroup \u002Fapp\u002Fnode_modules .\u002Fnode_modules\nCOPY --from=builder --chown=appuser:appgroup \u002Fapp\u002Fdist .\u002Fdist\nCOPY --from=builder --chown=appuser:appgroup \u002Fapp\u002Fpackage.json .\u002F\n\nENV NODE_ENV=production\nEXPOSE 3000\n\nHEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \\\n  CMD wget --no-verbose --tries=1 --spider http:\u002F\u002Flocalhost:3000\u002Fhealth || exit 1\n\nCMD [\"node\", \"dist\u002Fserver.js\"]\n```\n\n### 多阶段 Dockerfile (Go)\n\n```dockerfile\nFROM golang:1.22-alpine AS builder\nWORKDIR \u002Fapp\nCOPY go.mod go.sum .\u002F\nRUN go mod download\nCOPY . .\nRUN CGO_ENABLED=0 GOOS=linux go build -ldflags=\"-s -w\" -o \u002Fserver .\u002Fcmd\u002Fserver\n\nFROM alpine:3.19 AS runner\nRUN apk --no-cache add ca-certificates\nRUN adduser -D -u 1001 appuser\nUSER appuser\n\nCOPY --from=builder \u002Fserver \u002Fserver\n\nEXPOSE 8080\nHEALTHCHECK --interval=30s --timeout=3s CMD wget -qO- http:\u002F\u002Flocalhost:8080\u002Fhealth || exit 1\nCMD [\"\u002Fserver\"]\n```\n\n### 多阶段 Dockerfile (Python\u002FDjango)\n\n```dockerfile\nFROM python:3.12-slim AS builder\nWORKDIR \u002Fapp\nRUN pip install --no-cache-dir uv\nCOPY requirements.txt .\nRUN uv pip install --system --no-cache -r requirements.txt\n\nFROM python:3.12-slim AS runner\nWORKDIR \u002Fapp\n\nRUN useradd -r -u 1001 appuser\nUSER appuser\n\nCOPY --from=builder \u002Fusr\u002Flocal\u002Flib\u002Fpython3.12\u002Fsite-packages \u002Fusr\u002Flocal\u002Flib\u002Fpython3.12\u002Fsite-packages\nCOPY --from=builder \u002Fusr\u002Flocal\u002Fbin \u002Fusr\u002Flocal\u002Fbin\nCOPY . .\n\nENV PYTHONUNBUFFERED=1\nEXPOSE 8000\n\nHEALTHCHECK --interval=30s --timeout=3s CMD python -c \"import urllib.request; urllib.request.urlopen('http:\u002F\u002Flocalhost:8000\u002Fhealth\u002F')\" || exit 1\nCMD [\"gunicorn\", \"config.wsgi:application\", \"--bind\", \"0.0.0.0:8000\", \"--workers\", \"4\"]\n```\n\n### Docker 最佳实践\n\n```\n# 良好实践\n- 使用特定版本标签（node:22-alpine，而非 node:latest）\n- 采用多阶段构建以最小化镜像体积\n- 以非 root 用户身份运行\n- 优先复制依赖文件（利用分层缓存）\n- 使用 .dockerignore 排除 node_modules、.git、tests 等文件\n- 添加 HEALTHCHECK 指令\n- 在 docker-compose 或 k8s 中设置资源限制\n\n# 不良实践\n- 以 root 身份运行\n- 使用 :latest 标签\n- 在单个 COPY 层中复制整个仓库\n- 在生产镜像中安装开发依赖\n- 在镜像中存储密钥（应使用环境变量或密钥管理器）\n```\n\n## CI\u002FCD 流水线\n\n### GitHub Actions (标准流水线)\n\n```yaml\nname: CI\u002FCD\n\non:\n  push:\n    branches: [main]\n  pull_request:\n    branches: [main]\n\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: 22\n          cache: npm\n      - run: npm ci\n      - run: npm run lint\n      - run: npm run typecheck\n      - run: npm test -- --coverage\n      - uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with:\n          name: coverage\n          path: coverage\u002F\n\n  build:\n    needs: test\n    runs-on: ubuntu-latest\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: docker\u002Fsetup-buildx-action@v3\n      - uses: docker\u002Flogin-action@v3\n        with:\n          registry: ghcr.io\n          username: ${{ github.actor }}\n          password: ${{ secrets.GITHUB_TOKEN }}\n      - uses: docker\u002Fbuild-push-action@v5\n        with:\n          push: true\n          tags: ghcr.io\u002F${{ github.repository }}:${{ github.sha }}\n          cache-from: type=gha\n          cache-to: type=gha,mode=max\n\n  deploy:\n    needs: build\n    runs-on: ubuntu-latest\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    environment: production\n    steps:\n      - name: Deploy to production\n        run: |\n          # Platform-specific deployment command\n          # Railway: railway up\n          # Vercel: vercel --prod\n          # K8s: kubectl set image deployment\u002Fapp app=ghcr.io\u002F${{ github.repository }}:${{ github.sha }}\n          echo \"Deploying ${{ github.sha }}\"\n```\n\n### 流水线阶段\n\n```\nPR 已开启：\n  lint → typecheck → 单元测试 → 集成测试 → 预览部署\n\n合并到 main：\n  lint → typecheck → 单元测试 → 集成测试 → 构建镜像 → 部署到 staging → 冒烟测试 → 部署到 production\n```\n\n## 健康检查\n\n### 健康检查端点\n\n```typescript\n\u002F\u002F Simple health check\napp.get(\"\u002Fhealth\", (req, res) => {\n  res.status(200).json({ status: \"ok\" });\n});\n\n\u002F\u002F Detailed health check (for internal monitoring)\napp.get(\"\u002Fhealth\u002Fdetailed\", async (req, res) => {\n  const checks = {\n    database: await checkDatabase(),\n    redis: await checkRedis(),\n    externalApi: await checkExternalApi(),\n  };\n\n  const allHealthy = Object.values(checks).every(c => c.status === \"ok\");\n\n  res.status(allHealthy ? 200 : 503).json({\n    status: allHealthy ? \"ok\" : \"degraded\",\n    timestamp: new Date().toISOString(),\n    version: process.env.APP_VERSION || \"unknown\",\n    uptime: process.uptime(),\n    checks,\n  });\n});\n\nasync function checkDatabase(): Promise\u003CHealthCheck> {\n  try {\n    await db.query(\"SELECT 1\");\n    return { status: \"ok\", latency_ms: 2 };\n  } catch (err) {\n    return { status: \"error\", message: \"Database unreachable\" };\n  }\n}\n```\n\n### Kubernetes 探针\n\n```yaml\nlivenessProbe:\n  httpGet:\n    path: \u002Fhealth\n    port: 3000\n  initialDelaySeconds: 10\n  periodSeconds: 30\n  failureThreshold: 3\n\nreadinessProbe:\n  httpGet:\n    path: \u002Fhealth\n    port: 3000\n  initialDelaySeconds: 5\n  periodSeconds: 10\n  failureThreshold: 2\n\nstartupProbe:\n  httpGet:\n    path: \u002Fhealth\n    port: 3000\n  initialDelaySeconds: 0\n  periodSeconds: 5\n  failureThreshold: 30    # 30 * 5s = 150s max startup time\n```\n\n## 环境配置\n\n### 十二要素应用模式\n\n```bash\n# All config via environment variables — never in code\nDATABASE_URL=postgres:\u002F\u002Fuser:pass@host:5432\u002Fdb\nREDIS_URL=redis:\u002F\u002Fhost:6379\u002F0\nAPI_KEY=${API_KEY}           # injected by secrets manager\nLOG_LEVEL=info\nPORT=3000\n\n# Environment-specific behavior\nNODE_ENV=production          # or staging, development\nAPP_ENV=production           # explicit app environment\n```\n\n### 配置验证\n\n```typescript\nimport { z } from \"zod\";\n\nconst envSchema = z.object({\n  NODE_ENV: z.enum([\"development\", \"staging\", \"production\"]),\n  PORT: z.coerce.number().default(3000),\n  DATABASE_URL: z.string().url(),\n  REDIS_URL: z.string().url(),\n  JWT_SECRET: z.string().min(32),\n  LOG_LEVEL: z.enum([\"debug\", \"info\", \"warn\", \"error\"]).default(\"info\"),\n});\n\n\u002F\u002F Validate at startup — fail fast if config is wrong\nexport const env = envSchema.parse(process.env);\n```\n\n## 回滚策略\n\n### 即时回滚\n\n```bash\n# Docker\u002FKubernetes: point to previous image\nkubectl rollout undo deployment\u002Fapp\n\n# Vercel: promote previous deployment\nvercel rollback\n\n# Railway: redeploy previous commit\nrailway up --commit \u003Cprevious-sha>\n\n# Database: rollback migration (if reversible)\nnpx prisma migrate resolve --rolled-back \u003Cmigration-name>\n```\n\n### 回滚检查清单\n\n* \\[ ] 之前的镜像\u002F制品可用且已标记\n* \\[ ] 数据库迁移向后兼容（无破坏性更改）\n* \\[ ] 功能标志可以在不部署的情况下禁用新功能\n* \\[ ] 监控警报已配置，用于错误率飙升\n* \\[ ] 在生产发布前，回滚已在预演环境测试\n\n## 生产就绪检查清单\n\n在任何生产部署之前：\n\n### 应用\n\n* \\[ ] 所有测试通过（单元、集成、端到端）\n* \\[ ] 代码或配置文件中没有硬编码的密钥\n* \\[ ] 错误处理覆盖所有边缘情况\n* \\[ ] 日志是结构化的（JSON）且不包含 PII\n* \\[ ] 健康检查端点返回有意义的状态\n\n### 基础设施\n\n* \\[ ] Docker 镜像可重复构建（版本已固定）\n* \\[ ] 环境变量已记录并在启动时验证\n* \\[ ] 资源限制已设置（CPU、内存）\n* \\[ ] 水平伸缩已配置（最小\u002F最大实例数）\n* \\[ ] 所有端点均已启用 SSL\u002FTLS\n\n### 监控\n\n* \\[ ] 应用指标已导出（请求率、延迟、错误）\n* \\[ ] 已配置错误率超过阈值的警报\n* \\[ ] 日志聚合已设置（结构化日志，可搜索）\n* \\[ ] 健康端点有正常运行时间监控\n\n### 安全\n\n* \\[ ] 依赖项已扫描 CVE\n* \\[ ] CORS 仅配置允许的来源\n* \\[ ] 公共端点已启用速率限制\n* \\[ ] 身份验证和授权已验证\n* \\[ ] 安全头已设置（CSP、HSTS、X-Frame-Options）\n\n### 运维\n\n* \\[ ] 回滚计划已记录并测试\n* \\[ ] 数据库迁移已针对生产规模的数据进行测试\n* \\[ ] 常见故障场景的应急预案\n* \\[ ] 待命轮换和升级路径已定义\n","# 部署模式\n\n生产环境部署工作流和 CI\u002FCD 最佳实践。\n\n## 何时启用\n\n* 设置 CI\u002FCD 流水线时\n* 将应用容器化（Docker）时\n* 规划部署策略（蓝绿、金丝雀、滚动）时\n* 实现健康检查和就绪探针时\n* 准备生产发布时\n* 配置环境特定设置时\n\n## 部署策略\n\n### 滚动部署（默认）\n\n逐步替换实例——在发布过程中，新旧版本同时运行。\n\n```\n实例 1: v1 → v2  (首次更新)\n实例 2: v1        (仍在运行 v1)\n实例 3: v1        (仍在运行 v1)\n\n实例 1: v2\n实例 2: v1 → v2  (第二次更新)\n实例 3: v1\n\n实例 1: v2\n实例 2: v2\n实例 3: v1 → v2  (最后更新)\n```\n\n**优点：** 零停机时间，渐进式发布\n**缺点：** 两个版本同时运行——需要向后兼容的更改\n**适用场景：** 标准部署，向后兼容的更改\n\n### 蓝绿部署\n\n运行两个相同的环境。原子化地切换流量。\n\n```\nBlue  (v1) ← 流量\nGreen (v2)   空闲，运行新版本\n\n# 验证后：\nBlue  (v1)   空闲（转为备用状态）\nGreen (v2) ← 流量\n```\n\n**优点：** 即时回滚（切换回蓝色环境），切换干净利落\n**缺点：** 部署期间需要双倍的基础设施\n**适用场景：** 关键服务，对问题零容忍\n\n### 金丝雀部署\n\n首先将一小部分流量路由到新版本。\n\n```\nv1：95% 的流量\nv2：5% 的流量（金丝雀）\n\n# 如果指标表现良好：\nv1：50% 的流量\nv2：50% 的流量\n\n# 最终：\nv2：100% 的流量\n```\n\n**优点：** 在全量发布前，通过真实流量发现问题\n**缺点：** 需要流量分割基础设施和监控\n**适用场景：** 高流量服务，风险性更改，功能标志\n\n## Docker\n\n### 多阶段 Dockerfile (Node.js)\n\n```dockerfile\n# Stage 1: Install dependencies\nFROM node:22-alpine AS deps\nWORKDIR \u002Fapp\nCOPY package.json package-lock.json .\u002F\nRUN npm ci --production=false\n\n# Stage 2: Build\nFROM node:22-alpine AS builder\nWORKDIR \u002Fapp\nCOPY --from=deps \u002Fapp\u002Fnode_modules .\u002Fnode_modules\nCOPY . .\nRUN npm run build\nRUN npm prune --production\n\n# Stage 3: Production image\nFROM node:22-alpine AS runner\nWORKDIR \u002Fapp\n\nRUN addgroup -g 1001 -S appgroup && adduser -S appuser -u 1001\nUSER appuser\n\nCOPY --from=builder --chown=appuser:appgroup \u002Fapp\u002Fnode_modules .\u002Fnode_modules\nCOPY --from=builder --chown=appuser:appgroup \u002Fapp\u002Fdist .\u002Fdist\nCOPY --from=builder --chown=appuser:appgroup \u002Fapp\u002Fpackage.json .\u002F\n\nENV NODE_ENV=production\nEXPOSE 3000\n\nHEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \\\n  CMD wget --no-verbose --tries=1 --spider http:\u002F\u002Flocalhost:3000\u002Fhealth || exit 1\n\nCMD [\"node\", \"dist\u002Fserver.js\"]\n```\n\n### 多阶段 Dockerfile (Go)\n\n```dockerfile\nFROM golang:1.22-alpine AS builder\nWORKDIR \u002Fapp\nCOPY go.mod go.sum .\u002F\nRUN go mod download\nCOPY . .\nRUN CGO_ENABLED=0 GOOS=linux go build -ldflags=\"-s -w\" -o \u002Fserver .\u002Fcmd\u002Fserver\n\nFROM alpine:3.19 AS runner\nRUN apk --no-cache add ca-certificates\nRUN adduser -D -u 1001 appuser\nUSER appuser\n\nCOPY --from=builder \u002Fserver \u002Fserver\n\nEXPOSE 8080\nHEALTHCHECK --interval=30s --timeout=3s CMD wget -qO- http:\u002F\u002Flocalhost:8080\u002Fhealth || exit 1\nCMD [\"\u002Fserver\"]\n```\n\n### 多阶段 Dockerfile (Python\u002FDjango)\n\n```dockerfile\nFROM python:3.12-slim AS builder\nWORKDIR \u002Fapp\nRUN pip install --no-cache-dir uv\nCOPY requirements.txt .\nRUN uv pip install --system --no-cache -r requirements.txt\n\nFROM python:3.12-slim AS runner\nWORKDIR \u002Fapp\n\nRUN useradd -r -u 1001 appuser\nUSER appuser\n\nCOPY --from=builder \u002Fusr\u002Flocal\u002Flib\u002Fpython3.12\u002Fsite-packages \u002Fusr\u002Flocal\u002Flib\u002Fpython3.12\u002Fsite-packages\nCOPY --from=builder \u002Fusr\u002Flocal\u002Fbin \u002Fusr\u002Flocal\u002Fbin\nCOPY . .\n\nENV PYTHONUNBUFFERED=1\nEXPOSE 8000\n\nHEALTHCHECK --interval=30s --timeout=3s CMD python -c \"import urllib.request; urllib.request.urlopen('http:\u002F\u002Flocalhost:8000\u002Fhealth\u002F')\" || exit 1\nCMD [\"gunicorn\", \"config.wsgi:application\", \"--bind\", \"0.0.0.0:8000\", \"--workers\", \"4\"]\n```\n\n### Docker 最佳实践\n\n```\n# 良好实践\n- 使用特定版本标签（node:22-alpine，而非 node:latest）\n- 采用多阶段构建以最小化镜像体积\n- 以非 root 用户身份运行\n- 优先复制依赖文件（利用分层缓存）\n- 使用 .dockerignore 排除 node_modules、.git、tests 等文件\n- 添加 HEALTHCHECK 指令\n- 在 docker-compose 或 k8s 中设置资源限制\n\n# 不良实践\n- 以 root 身份运行\n- 使用 :latest 标签\n- 在单个 COPY 层中复制整个仓库\n- 在生产镜像中安装开发依赖\n- 在镜像中存储密钥（应使用环境变量或密钥管理器）\n```\n\n## CI\u002FCD 流水线\n\n### GitHub Actions (标准流水线)\n\n```yaml\nname: CI\u002FCD\n\non:\n  push:\n    branches: [main]\n  pull_request:\n    branches: [main]\n\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: 22\n          cache: npm\n      - run: npm ci\n      - run: npm run lint\n      - run: npm run typecheck\n      - run: npm test -- --coverage\n      - uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with:\n          name: coverage\n          path: coverage\u002F\n\n  build:\n    needs: test\n    runs-on: ubuntu-latest\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: docker\u002Fsetup-buildx-action@v3\n      - uses: docker\u002Flogin-action@v3\n        with:\n          registry: ghcr.io\n          username: ${{ github.actor }}\n          password: ${{ secrets.GITHUB_TOKEN }}\n      - uses: docker\u002Fbuild-push-action@v5\n        with:\n          push: true\n          tags: ghcr.io\u002F${{ github.repository }}:${{ github.sha }}\n          cache-from: type=gha\n          cache-to: type=gha,mode=max\n\n  deploy:\n    needs: build\n    runs-on: ubuntu-latest\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    environment: production\n    steps:\n      - name: Deploy to production\n        run: |\n          # Platform-specific deployment command\n          # Railway: railway up\n          # Vercel: vercel --prod\n          # K8s: kubectl set image deployment\u002Fapp app=ghcr.io\u002F${{ github.repository }}:${{ github.sha }}\n          echo \"Deploying ${{ github.sha }}\"\n```\n\n### 流水线阶段\n\n```\nPR 已开启：\n  lint → typecheck → 单元测试 → 集成测试 → 预览部署\n\n合并到 main：\n  lint → typecheck → 单元测试 → 集成测试 → 构建镜像 → 部署到 staging → 冒烟测试 → 部署到 production\n```\n\n## 健康检查\n\n### 健康检查端点\n\n```typescript\n\u002F\u002F Simple health check\napp.get(\"\u002Fhealth\", (req, res) => {\n  res.status(200).json({ status: \"ok\" });\n});\n\n\u002F\u002F Detailed health check (for internal monitoring)\napp.get(\"\u002Fhealth\u002Fdetailed\", async (req, res) => {\n  const checks = {\n    database: await checkDatabase(),\n    redis: await checkRedis(),\n    externalApi: await checkExternalApi(),\n  };\n\n  const allHealthy = Object.values(checks).every(c => c.status === \"ok\");\n\n  res.status(allHealthy ? 200 : 503).json({\n    status: allHealthy ? \"ok\" : \"degraded\",\n    timestamp: new Date().toISOString(),\n    version: process.env.APP_VERSION || \"unknown\",\n    uptime: process.uptime(),\n    checks,\n  });\n});\n\nasync function checkDatabase(): Promise\u003CHealthCheck> {\n  try {\n    await db.query(\"SELECT 1\");\n    return { status: \"ok\", latency_ms: 2 };\n  } catch (err) {\n    return { status: \"error\", message: \"Database unreachable\" };\n  }\n}\n```\n\n### Kubernetes 探针\n\n```yaml\nlivenessProbe:\n  httpGet:\n    path: \u002Fhealth\n    port: 3000\n  initialDelaySeconds: 10\n  periodSeconds: 30\n  failureThreshold: 3\n\nreadinessProbe:\n  httpGet:\n    path: \u002Fhealth\n    port: 3000\n  initialDelaySeconds: 5\n  periodSeconds: 10\n  failureThreshold: 2\n\nstartupProbe:\n  httpGet:\n    path: \u002Fhealth\n    port: 3000\n  initialDelaySeconds: 0\n  periodSeconds: 5\n  failureThreshold: 30    # 30 * 5s = 150s max startup time\n```\n\n## 环境配置\n\n### 十二要素应用模式\n\n```bash\n# All config via environment variables — never in code\nDATABASE_URL=postgres:\u002F\u002Fuser:pass@host:5432\u002Fdb\nREDIS_URL=redis:\u002F\u002Fhost:6379\u002F0\nAPI_KEY=${API_KEY}           # injected by secrets manager\nLOG_LEVEL=info\nPORT=3000\n\n# Environment-specific behavior\nNODE_ENV=production          # or staging, development\nAPP_ENV=production           # explicit app environment\n```\n\n### 配置验证\n\n```typescript\nimport { z } from \"zod\";\n\nconst envSchema = z.object({\n  NODE_ENV: z.enum([\"development\", \"staging\", \"production\"]),\n  PORT: z.coerce.number().default(3000),\n  DATABASE_URL: z.string().url(),\n  REDIS_URL: z.string().url(),\n  JWT_SECRET: z.string().min(32),\n  LOG_LEVEL: z.enum([\"debug\", \"info\", \"warn\", \"error\"]).default(\"info\"),\n});\n\n\u002F\u002F Validate at startup — fail fast if config is wrong\nexport const env = envSchema.parse(process.env);\n```\n\n## 回滚策略\n\n### 即时回滚\n\n```bash\n# Docker\u002FKubernetes: point to previous image\nkubectl rollout undo deployment\u002Fapp\n\n# Vercel: promote previous deployment\nvercel rollback\n\n# Railway: redeploy previous commit\nrailway up --commit \u003Cprevious-sha>\n\n# Database: rollback migration (if reversible)\nnpx prisma migrate resolve --rolled-back \u003Cmigration-name>\n```\n\n### 回滚检查清单\n\n* \\[ ] 之前的镜像\u002F制品可用且已标记\n* \\[ ] 数据库迁移向后兼容（无破坏性更改）\n* \\[ ] 功能标志可以在不部署的情况下禁用新功能\n* \\[ ] 监控警报已配置，用于错误率飙升\n* \\[ ] 在生产发布前，回滚已在预演环境测试\n\n## 生产就绪检查清单\n\n在任何生产部署之前：\n\n### 应用\n\n* \\[ ] 所有测试通过（单元、集成、端到端）\n* \\[ ] 代码或配置文件中没有硬编码的密钥\n* \\[ ] 错误处理覆盖所有边缘情况\n* \\[ ] 日志是结构化的（JSON）且不包含 PII\n* \\[ ] 健康检查端点返回有意义的状态\n\n### 基础设施\n\n* \\[ ] Docker 镜像可重复构建（版本已固定）\n* \\[ ] 环境变量已记录并在启动时验证\n* \\[ ] 资源限制已设置（CPU、内存）\n* \\[ ] 水平伸缩已配置（最小\u002F最大实例数）\n* \\[ ] 所有端点均已启用 SSL\u002FTLS\n\n### 监控\n\n* \\[ ] 应用指标已导出（请求率、延迟、错误）\n* \\[ ] 已配置错误率超过阈值的警报\n* \\[ ] 日志聚合已设置（结构化日志，可搜索）\n* \\[ ] 健康端点有正常运行时间监控\n\n### 安全\n\n* \\[ ] 依赖项已扫描 CVE\n* \\[ ] CORS 仅配置允许的来源\n* \\[ ] 公共端点已启用速率限制\n* \\[ ] 身份验证和授权已验证\n* \\[ ] 安全头已设置（CSP、HSTS、X-Frame-Options）\n\n### 运维\n\n* \\[ ] 回滚计划已记录并测试\n* \\[ ] 数据库迁移已针对生产规模的数据进行测试\n* \\[ ] 常见故障场景的应急预案\n* \\[ ] 待命轮换和升级路径已定义\n",{"name":5,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","everything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fdeployment-patterns",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill deployment-patterns",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill deployment-patterns",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill deployment-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fdeployment-patterns\u002FSKILL.md",true,[],[49,57,62,68,75,82],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":58,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":56},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":56},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":56},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":56},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":56},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]