[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EDFC01119QNBSJMGSV14SN":3,"skill-same:01M7EDFC01119QNBSJMGSV14SN":71},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7EDFC01119QNBSJMGSV14SN","render-docker",null,"在 Render 上构建并部署 Docker 容器——Dockerfile、多阶段构建、Blueprint 的 Docker 字段、私有 registry、层缓存及平台约束。当用户提到 Docker、Dockerfile、容器镜像、多阶段构建、容器 registry、GHCR、ECR、BuildKit、dockerContext、runtime docker 或 image，或要优化 Render 上的 Docker 构建时使用。","kael-odin\u002Fcodex-plugins-zh","kael-odin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F166499071?v=4","01M7EBHJT87XN88WT3PEQ8ZGZK","Kael Odin","01M7EBHJVC91GD7PGJN3ZB14SG",37,"MIT","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\r\nname: render-docker\ndescription: \"在 Render 上构建并部署 Docker 容器——Dockerfile、多阶段构建、Blueprint 的 Docker 字段、私有 registry、层缓存及平台约束。当用户提到 Docker、Dockerfile、容器镜像、多阶段构建、容器 registry、GHCR、ECR、BuildKit、dockerContext、runtime docker 或 image，或要优化 Render 上的 Docker 构建时使用。\"\nlicense: MIT\ncompatibility: >-\n  Any Render compute service (web, private, worker, cron) with runtime: docker\n  or runtime: image.\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: deployment\r\n---\r\n\r\n# Render Docker Deployments\r\n\r\nRender uses **BuildKit** for Docker builds. All compute service types that support custom runtimes can use **`runtime: docker`** (build from a Dockerfile in the repo) or **`runtime: image`** (pull a prebuilt image; no Dockerfile build on Render). Deeper patterns and copy-paste templates live under `references\u002F`.\r\n\r\n## When to Use\r\n\r\n- Authoring or debugging a **Dockerfile** for a Render service\r\n- Choosing **`runtime: docker`** vs **`runtime: image`** in a Blueprint\r\n- Wiring **private base images** or **prebuilt images** with registry credentials\r\n- **Multi-stage builds**, **build args**, **secrets**, and **layer caching**\r\n- **Performance** and **security** hardening of container images on Render\r\n\r\nFor full Blueprint authoring, see **render-blueprints**. For end-to-end deploy flows, see **render-deploy**.\r\n\r\n## Render Docker Builds\r\n\r\n- **BuildKit** is used for Docker builds on Render.\r\n- **`runtime: docker`**: Render builds an image from your repo using `dockerfilePath`, `dockerContext`, and optional `dockerCommand` (overrides image `CMD`).\r\n- **`runtime: image`**: Render pulls **`image.url`**; no repo-based image build. Pair with **`registryCredential`** when the registry is private.\r\n\r\n## Blueprint Configuration\r\n\r\n| Field | Role |\r\n|-------|------|\r\n| `dockerfilePath` | Path to the Dockerfile (default `.\u002FDockerfile`) |\r\n| `dockerContext` | Build context directory (what is sent to the daemon) |\r\n| `dockerCommand` | Overrides the container `CMD` after the image is built |\r\n| `image.url` | Image reference for `runtime: image` (registry\u002Frepo:tag or digest) |\r\n| `registryCredential` | Auth for private pulls; often `fromRegistryCreds` → Dashboard-stored credential |\r\n\r\nExample sketch (values illustrative):\r\n\r\n```yaml\r\nservices:\r\n  - type: web\r\n    name: api\r\n    runtime: docker\r\n    region: oregon\r\n    plan: starter\r\n    dockerfilePath: .\u002FDockerfile\r\n    dockerContext: .\r\n    dockerCommand: node server.js\r\n    envVars:\r\n      - key: PORT\r\n        value: 10000\r\n```\r\n\r\nFor `runtime: image`, set `image.url` and, if needed, `registryCredential` per **Registry Configuration** below.\r\n\r\n## Multi-Stage Builds\r\n\r\n**Recommended for production.** Use a **builder** stage for compilation and dependency installation, and a minimal **runner** stage that only copies artifacts and runtime files. Benefits:\r\n\r\n- Smaller images and faster pulls\r\n- Fewer tools and secrets in the final image (smaller attack surface)\r\n- Clear separation between build-time and run-time dependencies\r\n\r\nSee `references\u002Fdockerfile-patterns.md` for language-specific templates.\r\n\r\n## Build Args vs Secrets\r\n\r\n**Critical:** **Never pass secrets via `ARG`.** Build arguments are stored in image **layers** and can be recovered from the image history or intermediate layers.\r\n\r\n- Prefer **runtime environment variables** (Render **env vars** \u002F secret files) for application secrets.\r\n- For **build-time** secrets (e.g. private package feeds), use **Docker BuildKit secret mounts** (`RUN --mount=type=secret,...`) rather than `ARG`.\r\n\r\nTreat anything sensitive as **runtime** or **BuildKit secret mount**, not as a build arg.\r\n\r\n## Registry Configuration\r\n\r\nPrivate **base images** (for `runtime: docker`) or **prebuilt images** (`runtime: image`) need authentication:\r\n\r\n- Store credentials in the Render Dashboard under **Registry Credentials**.\r\n- In Blueprint, reference them with **`registryCredential.fromRegistryCreds.name`** (match the Dashboard name).\r\n\r\nSupports common registries (Docker Hub, GHCR, ECR, Google Artifact Registry, and others). Step-by-step per provider: `references\u002Fregistry-setup.md`.\r\n\r\n**Prebuilt image services** do **not** auto-deploy when the tag moves in the registry; trigger a **manual redeploy** or use a **deploy hook** when you publish a new image.\r\n\r\n## Layer Caching\r\n\r\n- Render **caches Docker layers** between builds; **order Dockerfile instructions** so that frequently unchanged layers stay early (see `references\u002Foptimization-guide.md`).\r\n- **Tags and caching:** mutable tags like **`latest`** can resolve to **stale cached** images. Prefer **immutable** references: **digest** (`repo\u002Fimage@sha256:...`) or **version pins** (`v1.2.3`).\r\n\r\n## Platform Specifics\r\n\r\n- Render builds **linux\u002Famd64**. Avoid assumptions about other architectures in production images.\r\n- **Port binding** matches native services: bind HTTP to **`0.0.0.0:$PORT`** (Render sets `PORT`).\r\n- **Health checks** behave like non-Docker web services (`healthCheckPath`, etc.).\r\n- **Secret files** from Render appear under **`\u002Fetc\u002Fsecrets\u002F`** — do not rely on repo-root secret paths inside the container unless you copy or mount them explicitly in the image.\r\n\r\n## `.dockerignore` and Start Commands\r\n\r\n- Always maintain a **`.dockerignore`** that excludes **`node_modules`**, **`.git`**, **`.env`**, build artifacts, logs, and OS junk. This shrinks context upload time and avoids leaking local files into layers. Lists and rationale: `references\u002Foptimization-guide.md`.\r\n- **Custom start command:** if you need multiple shell steps, use a single shell form, e.g. **`\u002Fbin\u002Fsh -c 'set -e; .\u002Fmigrate && exec node server.js'`** (prefer **`exec`** so your app receives signals for graceful shutdown).\r\n\r\n## References\r\n\r\n| Document | Contents |\r\n|----------|----------|\r\n| `references\u002Fdockerfile-patterns.md` | Multi-stage templates (Node, Python, Go, Ruby, Rust, static sites) |\r\n| `references\u002Fregistry-setup.md` | Docker Hub, GHCR, ECR, Artifact Registry + Blueprint wiring |\r\n| `references\u002Foptimization-guide.md` | Layer order, `.dockerignore`, BuildKit cache mounts, debugging |\r\n\r\n## Related Skills\r\n\r\n- **render-deploy** — Deploy flows, Blueprint vs Dashboard, operational steps\r\n- **render-blueprints** — Full `render.yaml` schema, wiring, and validation\r\n- **render-web-services** — Web service behavior, health checks, and HTTP edge cases\r\n","# Render Docker Deployments\r\n\r\nRender uses **BuildKit** for Docker builds. All compute service types that support custom runtimes can use **`runtime: docker`** (build from a Dockerfile in the repo) or **`runtime: image`** (pull a prebuilt image; no Dockerfile build on Render). Deeper patterns and copy-paste templates live under `references\u002F`.\r\n\r\n## When to Use\r\n\r\n- Authoring or debugging a **Dockerfile** for a Render service\r\n- Choosing **`runtime: docker`** vs **`runtime: image`** in a Blueprint\r\n- Wiring **private base images** or **prebuilt images** with registry credentials\r\n- **Multi-stage builds**, **build args**, **secrets**, and **layer caching**\r\n- **Performance** and **security** hardening of container images on Render\r\n\r\nFor full Blueprint authoring, see **render-blueprints**. For end-to-end deploy flows, see **render-deploy**.\r\n\r\n## Render Docker Builds\r\n\r\n- **BuildKit** is used for Docker builds on Render.\r\n- **`runtime: docker`**: Render builds an image from your repo using `dockerfilePath`, `dockerContext`, and optional `dockerCommand` (overrides image `CMD`).\r\n- **`runtime: image`**: Render pulls **`image.url`**; no repo-based image build. Pair with **`registryCredential`** when the registry is private.\r\n\r\n## Blueprint Configuration\r\n\r\n| Field | Role |\r\n|-------|------|\r\n| `dockerfilePath` | Path to the Dockerfile (default `.\u002FDockerfile`) |\r\n| `dockerContext` | Build context directory (what is sent to the daemon) |\r\n| `dockerCommand` | Overrides the container `CMD` after the image is built |\r\n| `image.url` | Image reference for `runtime: image` (registry\u002Frepo:tag or digest) |\r\n| `registryCredential` | Auth for private pulls; often `fromRegistryCreds` → Dashboard-stored credential |\r\n\r\nExample sketch (values illustrative):\r\n\r\n```yaml\r\nservices:\r\n  - type: web\r\n    name: api\r\n    runtime: docker\r\n    region: oregon\r\n    plan: starter\r\n    dockerfilePath: .\u002FDockerfile\r\n    dockerContext: .\r\n    dockerCommand: node server.js\r\n    envVars:\r\n      - key: PORT\r\n        value: 10000\r\n```\r\n\r\nFor `runtime: image`, set `image.url` and, if needed, `registryCredential` per **Registry Configuration** below.\r\n\r\n## Multi-Stage Builds\r\n\r\n**Recommended for production.** Use a **builder** stage for compilation and dependency installation, and a minimal **runner** stage that only copies artifacts and runtime files. Benefits:\r\n\r\n- Smaller images and faster pulls\r\n- Fewer tools and secrets in the final image (smaller attack surface)\r\n- Clear separation between build-time and run-time dependencies\r\n\r\nSee `references\u002Fdockerfile-patterns.md` for language-specific templates.\r\n\r\n## Build Args vs Secrets\r\n\r\n**Critical:** **Never pass secrets via `ARG`.** Build arguments are stored in image **layers** and can be recovered from the image history or intermediate layers.\r\n\r\n- Prefer **runtime environment variables** (Render **env vars** \u002F secret files) for application secrets.\r\n- For **build-time** secrets (e.g. private package feeds), use **Docker BuildKit secret mounts** (`RUN --mount=type=secret,...`) rather than `ARG`.\r\n\r\nTreat anything sensitive as **runtime** or **BuildKit secret mount**, not as a build arg.\r\n\r\n## Registry Configuration\r\n\r\nPrivate **base images** (for `runtime: docker`) or **prebuilt images** (`runtime: image`) need authentication:\r\n\r\n- Store credentials in the Render Dashboard under **Registry Credentials**.\r\n- In Blueprint, reference them with **`registryCredential.fromRegistryCreds.name`** (match the Dashboard name).\r\n\r\nSupports common registries (Docker Hub, GHCR, ECR, Google Artifact Registry, and others). Step-by-step per provider: `references\u002Fregistry-setup.md`.\r\n\r\n**Prebuilt image services** do **not** auto-deploy when the tag moves in the registry; trigger a **manual redeploy** or use a **deploy hook** when you publish a new image.\r\n\r\n## Layer Caching\r\n\r\n- Render **caches Docker layers** between builds; **order Dockerfile instructions** so that frequently unchanged layers stay early (see `references\u002Foptimization-guide.md`).\r\n- **Tags and caching:** mutable tags like **`latest`** can resolve to **stale cached** images. Prefer **immutable** references: **digest** (`repo\u002Fimage@sha256:...`) or **version pins** (`v1.2.3`).\r\n\r\n## Platform Specifics\r\n\r\n- Render builds **linux\u002Famd64**. Avoid assumptions about other architectures in production images.\r\n- **Port binding** matches native services: bind HTTP to **`0.0.0.0:$PORT`** (Render sets `PORT`).\r\n- **Health checks** behave like non-Docker web services (`healthCheckPath`, etc.).\r\n- **Secret files** from Render appear under **`\u002Fetc\u002Fsecrets\u002F`** — do not rely on repo-root secret paths inside the container unless you copy or mount them explicitly in the image.\r\n\r\n## `.dockerignore` and Start Commands\r\n\r\n- Always maintain a **`.dockerignore`** that excludes **`node_modules`**, **`.git`**, **`.env`**, build artifacts, logs, and OS junk. This shrinks context upload time and avoids leaking local files into layers. Lists and rationale: `references\u002Foptimization-guide.md`.\r\n- **Custom start command:** if you need multiple shell steps, use a single shell form, e.g. **`\u002Fbin\u002Fsh -c 'set -e; .\u002Fmigrate && exec node server.js'`** (prefer **`exec`** so your app receives signals for graceful shutdown).\r\n\r\n## References\r\n\r\n| Document | Contents |\r\n|----------|----------|\r\n| `references\u002Fdockerfile-patterns.md` | Multi-stage templates (Node, Python, Go, Ruby, Rust, static sites) |\r\n| `references\u002Fregistry-setup.md` | Docker Hub, GHCR, ECR, Artifact Registry + Blueprint wiring |\r\n| `references\u002Foptimization-guide.md` | Layer order, `.dockerignore`, BuildKit cache mounts, debugging |\r\n\r\n## Related Skills\r\n\r\n- **render-deploy** — Deploy flows, Blueprint vs Dashboard, operational steps\r\n- **render-blueprints** — Full `render.yaml` schema, wiring, and validation\r\n- **render-web-services** — Web service behavior, health checks, and HTTP edge cases\r\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"author":25,"version":26,"category":27},"Render","1.0.0","deployment","Any Render compute service (web, private, worker, cron) with runtime: docker or runtime: image.","main","e3091d1b371a9dcd9455d333175f948b286fdfcf","plugins\u002Frender\u002Fskills\u002Frender-docker",1,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh","https:\u002F\u002Fkael-odin.github.io\u002Fcodex-plugins-zh\u002F","https:\u002F\u002Fgithub.com\u002Fkael-odin","https:\u002F\u002Fkael-odin.github.io\u002Fodin-valhalla\u002F","Full-stack development • Open-source • System engineering\r\nTurning ideas into repositories.","2026-11-08 17:05:36",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add kael-odin\u002Fcodex-plugins-zh --skill render-docker",{"tool":45,"command":46},"bunx","bunx skills add kael-odin\u002Fcodex-plugins-zh --skill render-docker",{"tool":48,"command":49},"pnpm","pnpm dlx skills add kael-odin\u002Fcodex-plugins-zh --skill render-docker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002FSKILL.md",true,[53,59,63,67],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"agents\u002Fopenai.yaml","REFERENCE","参考文档",208,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002Fagents\u002Fopenai.yaml",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fdockerfile-patterns.md",5683,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002Freferences\u002Fdockerfile-patterns.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Foptimization-guide.md",3375,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002Freferences\u002Foptimization-guide.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fregistry-setup.md",3200,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-docker\u002Freferences\u002Fregistry-setup.md",[72,81,88,96,103,110],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7EDVCKB89EF755PQMKV1BZA","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7EDPX7WHN6HQZ0QKWB0BGVZ","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7EDHHD98T8ZH09F40Q973G3","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7EDH3SGVMS1AFS6Q40B5J48","render-workflows","搭建、开发、测试和部署 Render Workflows。涵盖首次脚手架搭建（通过 CLI 或手动方式）、SDK 安装（Python 或 TypeScript）、任务模式（重试、子任务、扇出）、本地开发、控制台部署和故障排查。适用于用户首次搭建 Render Workflows、构建工作流服务、添加或修改工作流任务、本地测试工作流或部署到 Render 的场景。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7EDH0CYEKQ4VVARHZAQ43S8","render-web-services","配置 Render web service——端口绑定、TLS、健康检查、自定义域名、自动部署、PR 预览、持久化磁盘及部署生命周期。当用户需要搭建 web service、修复健康检查失败、添加自定义域名、配置零停机部署，或排查端口绑定问题时使用。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7EDGVDYFBG1CKSNMQ2DD336","render-static-sites","在 Render 全球 CDN 上部署并配置静态站点——构建命令、发布路径、SPA 路由、重定向、自定义 header 及 PR 预览。当用户需要部署静态站点、搭建 React\u002FVue\u002FHugo\u002FGatsby 前端、配置 SPA 回退路由、添加重定向规则、自定义响应 header，或在静态站点与 web service 之间为前端做选择时使用。触发词:static site、CDN、SPA、single-page app、React deploy、Vue deploy、Hugo、Gatsby、Docusaurus、Jekyll、staticPublishPath。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]