render-disks

Configures and manages persistent disks on Render services including mount paths, sizing, and snapshots.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/greenmartialarts/EventCore --skill render-disks-greenmartialarts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-disks
Source: https://github.com/greenmartialarts/EventCore/tree/main/.junie/skills/render-disks
Command: npx skills add https://github.com/greenmartialarts/EventCore --skill render-disks-greenmartialarts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Render services have an ephemeral filesystem by default, so all local file changes are lost on every deploy. This Skill guides you through attaching persistent disks to preserve uploads, databases, and stateful data across deploys and restarts. ## Core Features & Use Cases - Disk Setup: Attach disks via the Render Dashboard or Blueprint render.yaml with correct mount paths and sizes. - Constraint Guidance: Understand single-instance limits, disabled zero-downtime deploys, and disallowed mount paths before committing to a disk. - Snapshots & Transfers: Manage automatic 24-hour snapshots, full restores, and file transfers via SCP or magic-wormhole. - Use Case: You are deploying a WordPress CMS on Render and need media uploads to survive redeploys—attach a 10 GB disk at /var/data and plan for single-instance operation. ## Quick Start Ask the assistant to attach a persistent disk to your Render web service with a mount path and size appropriate for your runtime.

Frequently Asked Questions about render-disks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a persistent disk to a Render service?

Add a persistent disk from your service's Disks page in the Render Dashboard by setting a mount path and size in GB, or declare a `disk` block with name, mountPath, and sizeGB in your render.yaml Blueprint. Adding a disk triggers a new deploy.

Can a Render service with a disk scale to multiple instances?

No, services with an attached disk are limited to a single instance and cannot use autoscaling. Zero-downtime deploys are also disabled, so each deploy causes brief downtime while the old instance stops before the new one starts.

Why is my Render disk not accessible during the build command?

Disks are only mounted at runtime; buildCommand and preDeployCommand run on separate compute without disk access. Move any logic that reads or writes disk data into your start command instead.

Should I use a Render disk or Render Postgres for my database?

Prefer Render Postgres for relational databases because it provides managed backups, point-in-time recovery, and replicas. Disks suit self-managed databases like MySQL or MongoDB, but use database-native dump tools rather than disk snapshots for recovery.

Can I decrease the size of a Render disk after creating it?

No, disk size can be increased at any time without downtime but can never be decreased. Start with the smallest viable size, such as 1-5 GB for small upload workloads, and grow as needed.

How do I transfer files to and from a Render disk?

Transfer files using SCP over SSH with the service's ssh.YOUR_REGION.render.com address, or use magic-wormhole, which is preinstalled on native runtimes. SCP requires SSH access enabled for the service.