ericrisco/rsc-harness / skills/render
render
VerifiedUse when deploying or fixing an app on Render — web services, background workers, cron jobs, private services, managed Postgres and Key-Value, and especially the render.yaml Blueprint. Covers deploys that fail with no open ports detected, 502s on first deploy, free-tier cold starts, and a free Postgres about to expire with its data. NOT the generic ship and release flow (that is `deployment`), NOT another PaaS such as `railway` or `fly-io`.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.9 KB |
| evals/README.md | markdown | 834 B |
| evals/cases.yaml | config | 3.7 KB |
| references/blueprint-reference.md | markdown | 6.7 KB |
| scripts/verify.shexecutable | script | 5.5 KB |
references/blueprint-reference.md
View on GitHub# render.yaml — full key reference and recipes
The exhaustive Blueprint surface. Dated 2026-06-02 against render.com/docs/blueprint-spec.
Pull the key you need; copy a recipe and adapt.
## Top-level keys
| Key | What |
| --- | --- |
| `services` | every web / pserv / worker / cron / keyvalue service |
| `databases` | managed Postgres instances |
| `envVarGroups` | named, reusable env var bundles shared across services |
| `projects` | group services into a Render project |
| `previews` | preview-environment config (`generation: automatic \| manual \| off`) |
## Common service keys (web / pserv / worker / cron)
| Key | Notes |
| --- | --- |
| `type` | `web` \| `pserv` \| `worker` \| `cron` \| `keyvalue` |
| `name` | unique within the workspace |
| `runtime` | `node` \| `python` \| `docker` \| `image` \| `static` \| `go` \| `ruby` \| `elixir` \| `rust` (required except `keyvalue`) |
| `region` | `oregon` \| `ohio` \| `virginia` \| `frankfurt` \| `singapore` |
| `plan` | `free` \| `starter` \| `standard` \| `pro` \| `pro plus` \| `pro max` \| `pro ultra` |
| `buildCommand` | build step (native runtimes) |
| `startCommand` | process entrypoint |
| `preDeployCommand` | runs once before the new instance serves traffic — migrations |
| `healthCheckPath` | path Render polls to gate zero-downtime rollout (web only) |
| `autoDeployTrigger` | `commit` \| `checksPass` \| `off` |
| `numInstances` | fixed replica count |
| `scaling` | `{ minInstances, maxInstances, targetCPUPercent, targetMemoryPercent }` |
| `disk` | `{ name, mountPath, sizeGB }` — pins to a single instance |
| `rootDir` | subdirectory to treat as the build root (monorepos) |
| `buildFilter` | `{ paths, ignoredPaths }` — only deploy when matching files change |
| `envVars` | env var list (see reference forms below) |
### Docker-runtime keys
| Key | Notes |
| --- | --- |
| `runtime: docker` | build from a Dockerfile in the repo |
| `dockerfilePath` | path to the Dockerfile (e.g. `./apps/api/Dockerfile`) |
| `dockerContext` | build context directory |
| `runtime: image` | deploy a prebuilt image — `image: { url, creds }` |
### Static-site keys (`runtime: static`)
| Key | Notes |
| --- | --- |
| `staticPublishPath` | directory of built assets (e.g. `dist`, `build`, `out`) |
| `routes` | rewrite/redirect rules: `{ type: rewrite \| redirect, source, destination }` |
| `headers` | `{ path, name, value }` custom response headers |
### Cron-only keys
| Key | Notes |
| --- | --- |
| `schedule` | **required** cron expression; run killed after 12h; one active run at a time |
## envVars reference forms
| Form | Resolves to |
| --- | --- |
| `{ key, value }` | a literal (avoid for secrets) |
| `{ key, sync: false }` | typed once at setup, not stored in the repo |
| `{ key, generateValue: true }` | random secret Render generates and stores |
| `{ key, fromDatabase: { name, property } }` | `property`: `connectionString`, `host`, `port`, `user`, `password`, `database` |
| `{ key, fromService: { name, type, property } }` | `property`: `hostport`, `host`, `port` (and for keyvalue, `connectionString`) |
| `{ fromGroup: <name> }` | pull a whole env var group |
## Database keys (`databases:`)
| Key | Notes |
| --- | --- |
| `name` | unique name |
| `plan` | `free` (expires 30 days after creation, 14-day grace, one per workspace) \| `starter` \| `standard` \| … |
| `postgresMajorVersion` | e.g. `"17"` |
| `region` | same enum as services |
| `diskSizeGB` | storage size |
| `databaseName` / `user` | optional explicit names |
| `readReplicas` | `[{ name }]` read-replica list |
| `highAvailability` | `{ enabled: true }` (paid) |
| `previewPlan` | plan used for preview-env databases |
| `ipAllowList` | `[{ source, description }]` — `0.0.0.0/0` for public, omit for internal-only |
## Recipe 1 — Next.js web + Postgres
```yaml
databases:
- name: web-db
plan: starter
postgresMajorVersion: "17"
services:
- type: web
name: nextjs-app
runtime: node
plan: starter
buildCommand: npm ci && npm run build
startCommand: npm start # next start binds 0.0.0.0:$PORT by default
healthCheckPath: /api/health
preDeployCommand: npx prisma migrate deploy
envVars:
- key: DATABASE_URL
fromDatabase: { name: web-db, property: connectionString }
- key: NEXTAUTH_SECRET
generateValue: true
- key: NODE_ENV
value: production
```
## Recipe 2 — FastAPI web + worker + cron + Key Value
```yaml
databases:
- name: api-db
plan: starter
postgresMajorVersion: "17"
services:
- type: keyvalue
name: cache
plan: starter
ipAllowList: [] # internal only
- type: web
name: api
runtime: python
plan: starter
buildCommand: pip install -r requirements.txt
startCommand: gunicorn -k uvicorn.workers.UvicornWorker app.main:app --bind 0.0.0.0:$PORT
healthCheckPath: /health
preDeployCommand: alembic upgrade head
envVars:
- key: DATABASE_URL
fromDatabase: { name: api-db, property: connectionString }
- key: REDIS_URL
fromService: { name: cache, type: keyvalue, property: connectionString }
- type: worker
name: tasks
runtime: python
plan: starter
buildCommand: pip install -r requirements.txt
startCommand: celery -A app.worker worker -l info
envVars:
- key: DATABASE_URL
fromDatabase: { name: api-db, property: connectionString }
- key: REDIS_URL
fromService: { name: cache, type: keyvalue, property: connectionString }
- type: cron
name: send-digest
runtime: python
schedule: "*/5 * * * *" # every 5 minutes
buildCommand: pip install -r requirements.txt
startCommand: python -m app.jobs.digest
envVars:
- key: DATABASE_URL
fromDatabase: { name: api-db, property: connectionString }
```
## Recipe 3 — Docker monorepo (rootDir + dockerfilePath + buildFilter)
```yaml
services:
- type: web
name: api
runtime: docker
rootDir: apps/api
dockerfilePath: apps/api/Dockerfile
buildFilter:
paths:
- apps/api/**
- packages/shared/** # only redeploy when these change
plan: starter
healthCheckPath: /healthz
envVars:
- key: PORT
value: "10000" # your Dockerfile CMD must bind 0.0.0.0:$PORT
```
## Recipe 4 — static SPA with rewrites and headers
```yaml
services:
- type: web
name: spa
runtime: static
buildCommand: npm ci && npm run build
staticPublishPath: dist
routes:
- type: rewrite
source: /*
destination: /index.html # SPA fallback so client routing works
headers:
- path: /*
name: X-Frame-Options
value: DENY
- path: /assets/*
name: Cache-Control
value: public, max-age=31536000, immutable
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |