What problem does it solve? Render services use an ephemeral filesystem by default, so all local file changes are lost on every deploy or restart. This Skill guides you through attaching persistent disks so uploads, databases, and stateful data survive deployments. ## Core Features & Use Cases - Disk Setup & Configuration: Attach disks via the Dashboard or Blueprint (render.yaml) with correct mount paths per runtime (Node.js, Go, Docker) and avoid disallowed paths. - Constraint Awareness: Understand critical limits—single instance only, no zero-downtime deploys, no build-time disk access, and size can grow but never shrink. - Snapshots & File Transfers: Use automatic 24-hour snapshots with 7-day retention, full restores, and SCP or magic-wormhole file transfers. - Use Case: Deploy a WordPress CMS on Render with media uploads persisted at /var/data, sized at 10 GB, while understanding why horizontal scaling is disabled. ## Quick Start Ask the assistant to attach a 10 GB persistent disk mounted at /var/data to my Render web service using a Blueprint.