What problem does it solve? Deploying web services on Render involves many interacting settings—port binding, health checks, TLS, custom domains, auto-deploy triggers, and persistent disks—and misconfiguring any of them causes deploys that never go live, failed health checks, or unexpected downtime. This Skill provides the operational knowledge to configure and debug Render Web Services correctly. ## Core Features & Use Cases - Port Binding & TLS Guidance: Explains binding to 0.0.0.0 on the PORT environment variable, reserved ports, multi-port private networking, and edge TLS termination. - Health Checks & Deploy Lifecycle: Covers healthCheckPath configuration, 2xx/3xx success criteria, pre-deploy commands, zero-downtime swaps, drain behavior with maxShutdownDelaySeconds, and rollbacks. - Domains, Disks & Auto-Deploy: Details CNAME/apex/wildcard domain setup, autoDeployTrigger modes (commit, checksPass, off), PR previews, and persistent disk constraints (single instance, no zero-downtime). - Use Case: Your Render deploy succeeds in the Dashboard but never takes traffic. Use this Skill to diagnose that the app was bound to 127.0.0.1 instead of 0.0.0.0, or that the health check path returns a 404, and fix the configuration. ## Quick Start Ask the assistant to help configure a Render web service health check and explain why your deploy is not going live.