render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
- License 许可
- MIT
- 最近更新
- 2026-07-19
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- render-web-services
- license
- MIT
- metadata
- { "author": "Render", "version": "1.0.0", "category": "compute" }
- description
- Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
- compatibility
- Render web services (native runtimes or Docker)
02 资源文件 4
- 参考文档agents/openai.yaml213 B
- 参考文档references/custom-domains.md2.7 KB
- 参考文档references/deploy-lifecycle.md3.7 KB
- 参考文档references/health-check-patterns.md3.0 KB
03 SKILL.md 正文
Render Web Services
This skill covers Web Service behavior on Render: how traffic reaches your process, how deploys go live, and how optional features (domains, disks, auto-deploy) interact. Use it alongside Blueprint and networking skills when wiring render.yaml or Dashboard settings.
When to Use
- Configuring or debugging port binding, PORT, or multi-port web services
- TLS/HTTPS expectations at the edge vs inside the container
- Health checks blocking or rolling back deploys
- Custom domains, DNS, and certificate provisioning
- Auto-deploy, CI-gated deploys, and PR preview generation
- Persistent disks and their impact on scaling and zero-downtime
- Deploy lifecycle: build, pre-deploy, swap, drain, rollback, shutdown delay
Deeper patterns live under references/ (health checks, domains, deploy phases).
Port Binding
- Listen on
0.0.0.0(all interfaces). Binding only tolocalhostor127.0.0.1prevents Render’s proxy from reaching your app. - Use the
PORTenvironment variable for the HTTP listen port. Render sets it for you; the default is often10000and you can change the configured value in the service Settings in the Dashboard. - Reserved ports (do not bind your application to these for normal traffic):
18012,18013,19099.
Multi-port Web Services
- Only one port receives public HTTP traffic: the port aligned with
PORT. - Additional open ports are reachable on Render’s private network only (not from the public internet through the same public URL pattern).
TLS and HTTPS
- TLS terminates at Render’s edge. The edge speaks HTTPS to clients; your process typically receives plain HTTP on
PORT. - HTTPS redirect for clients is handled by the platform; users hitting HTTP are redirected appropriately at the edge.
- Do not terminate TLS inside the app for the primary public listener unless you have a rare, explicit need—standard Web Services assume HTTP behind the proxy.
Health Checks
- Configure a path via
healthCheckPathin a Blueprint or the Health Check Path field in the Dashboard. - Render issues HTTP GET requests to that path. Responses must be
2xxor3xxfor success. - Failed health checks prevent a new deploy from going live (the deploy does not succeed in taking production traffic as expected).
- Render probes on a repeat interval with a per-request timeout; both are configurable in service settings (see Dashboard). Failed checks during rollout prevent the new revision from receiving traffic.
- Check frequency, timeouts, and tuning guidance in
references/health-check-patterns.md.
Custom Domains
- Point DNS with a CNAME to
[service-name].onrender.com(use your service’s hostname from the Dashboard). - Render automatically provisions and renews TLS certificates for verified domains.
- Apex (root) domains need provider-specific CNAME-like or flattened records where plain CNAME at
@is unsupported. - Wildcard domains (e.g.
*.example.com) are supported when configured and verified. - Multiple custom domains per service are supported; Blueprints can list them under the
domainsfield.
See references/custom-domains.md for Dashboard steps, verification, and troubleshooting.
Auto-Deploy and PR Previews
autoDeployTrigger(Blueprint) / auto-deploy settings control when production deploys run:commit— deploy on every push to the tracked branchchecksPass— deploy only when required Git checks passoff— manual deploys only (Dashboard, CLI, hooks)
- PR previews are configured under Blueprint
previews.generation(and related preview settings); generation behavior depends on repo integration and plan.
Persistent Disks
- Attach disks via the
diskfield in a Blueprint (or equivalent Dashboard storage settings). - A service with an attached persistent disk is single-instance only: horizontal scaling is not available in that configuration.
- Zero-downtime deploys are disabled when a persistent disk is attached—deploys follow a different rollout pattern.
- Disk size increases are allowed; decreases are not.
- The disk is not mounted during the build phase—only at runtime in the running service.
Deploy Lifecycle
Typical flow:
- Build — clone repo, run
buildCommand, produce the runnable artifact/image. - Pre-deploy command (optional) — runs in the new image before traffic switches; use for migrations. If it fails, the deploy is canceled.
- Deploy — new instances start; health checks must pass before traffic moves.
- Zero-downtime swap (when applicable) — traffic shifts to new instances; old instances drain in-flight work.
maxShutdownDelaySeconds(range 1–300, default 30) bounds how long old instances may continue handling requests during drain before shutdown.- Rollbacks — revert to a previous successful deploy from the Dashboard.
Full sequence, hooks, filters, and CLI notes: references/deploy-lifecycle.md.
Free Tier Notes
Free Web Services have separate limits: e.g. no custom domains on the free instance type, and services spin down after inactivity (cold starts on next request). Treat free-tier behavior as distinct from paid Web Service defaults when advising on domains, uptime, and scaling.
References
| Topic | File |
|---|---|
| Health check design, timeouts, pitfalls | references/health-check-patterns.md |
| Domains, DNS, TLS verification | references/custom-domains.md |
| Build, pre-deploy, drain, rollbacks, triggers | references/deploy-lifecycle.md |
Related Skills
- render-deploy — Blueprints, first-time deploy,
render.yamlstructure - render-docker — Docker-based Web Services and image/runtime details
- render-networking — Private network, internal URLs, multi-port private listeners
- render-scaling — Instance counts, plans, and scaling constraints (including disk interactions)
04 同仓库更多 Skills
Zotero
Use Zotero Desktop from Codex to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX/RIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.
zoom-apps-sdk
Use when using Apps SDK.
youtube
Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript. Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or "what does this video actually say". The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content. Triggers: "youtube transcript", "get the transcript of this video", "summarize this youtube video", "what did they say in https://youtube.com/...", "key claims from this talk".
yeet
Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.
x-post-creator
Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, /x-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs/x-posts/[story-name]/.
x-api
Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X/x.com, reading threads and replies, creating lists, staging/publishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions /x-api or "search X".