davila7/claude-code-templates / cli-tool/components/skills/development/render-deploy
render-deploy
FlaggedDeploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 10.5 KB |
| SKILL.md | skill md | 17.2 KB |
| agents/openai.yaml | config | 480 B |
| assets/docker.yaml | config | 1.4 KB |
| assets/go-api.yaml | config | 848 B |
| assets/nextjs-postgres.yaml | config | 870 B |
| assets/node-express.yaml | config | 619 B |
| assets/python-django.yaml | config | 2.5 KB |
| assets/render-small.svg | other | 553 B |
| assets/render.png | binary | 911 B |
| assets/static-site.yaml | config | 1.3 KB |
| references/blueprint-spec.md | markdown | 15.6 KB |
| references/codebase-analysis.md | markdown | 2.2 KB |
| references/configuration-guide.md | markdown | 11.4 KB |
| references/deployment-details.md | markdown | 5.2 KB |
| references/direct-creation.md | markdown | 2.7 KB |
| references/error-patterns.md | markdown | 833 B |
| references/post-deploy-checks.md | markdown | 1.0 KB |
| references/runtimes.md | markdown | 9.6 KB |
| references/service-types.md | markdown | 11.8 KB |
| references/troubleshooting-basics.md | markdown | 1.3 KB |
references/deployment-details.md
View on GitHub# Deployment Details
Use this reference for service discovery, configuration patterns, quick commands, and common issues.
## Service Discovery
**List all services:**
```
list_services()
```
Returns all services with IDs, names, types, and status.
**Get specific service details:**
```
get_service(serviceId: "<id>")
```
Returns full configuration including environment variables and build/start commands.
**List PostgreSQL databases:**
```
list_postgres_instances()
```
**List Key-Value stores:**
```
list_key_value()
```
## Configuration Details
### Environment Variables
**All environment variables must be declared in render.yaml.**
**Three patterns for environment variables:**
1. **Hardcoded values** (non-sensitive configuration):
```yaml
envVars:
- key: NODE_ENV
value: production
- key: API_URL
value: https://api.example.com
```
2. **Database connections** (auto-generated):
```yaml
envVars:
- key: DATABASE_URL
fromDatabase:
name: postgres
property: connectionString
- key: REDIS_URL
fromDatabase:
name: redis
property: connectionString
```
3. **Secrets** (user fills in Dashboard):
```yaml
envVars:
- key: JWT_SECRET
sync: false
- key: API_KEY
sync: false
- key: STRIPE_SECRET_KEY
sync: false
```
Complete environment variable guide: [configuration-guide.md](configuration-guide.md)
### Port Binding
**CRITICAL:** Web services must bind to `0.0.0.0:$PORT` (NOT `localhost`). Render sets the `PORT` environment variable.
**Node.js Example:**
```javascript
const PORT = process.env.PORT || 3000;
app.listen(PORT, '0.0.0.0', () => {
console.log(`Server running on port ${PORT}`);
});
```
**Python Example:**
```python
import os
port = int(os.environ.get('PORT', 5000))
app.run(host='0.0.0.0', port=port)
```
**Go Example:**
```go
port := os.Getenv("PORT")
if port == "" {
port = "3000"
}
http.ListenAndServe(":"+port, handler)
```
### Plan Defaults
**Use `plan: free` unless the user specifies otherwise.** Refer to Render pricing for current limits and capacity.
### Build Commands
**Use non-interactive flags to prevent build hangs:**
- npm: `npm ci`
- yarn: `yarn install --frozen-lockfile`
- pnpm: `pnpm install --frozen-lockfile`
- bun: `bun install --frozen-lockfile`
- pip: `pip install -r requirements.txt`
- uv: `uv sync`
- apt: `apt-get install -y <package>`
- bundler: `bundle install --jobs=4 --retry=3`
### Database Connections
When services connect to databases in the same Render account, use `fromDatabase` references for internal URLs.
### Health Checks
Optional but recommended: add a `/health` endpoint for faster deployment detection.
## Quick Reference
### MCP Tools (Preferred)
```
# Service Discovery
list_services()
get_service(serviceId: "<id>")
list_postgres_instances()
list_key_value()
# Service Creation
create_web_service(name, runtime, buildCommand, startCommand, ...)
create_static_site(name, buildCommand, publishPath, ...)
create_cron_job(name, runtime, schedule, buildCommand, startCommand, ...)
create_postgres(name, plan, region)
create_key_value(name, plan, region)
# Environment Variables
update_environment_variables(serviceId, envVars: [{key, value}, ...])
# Deployment & Monitoring
list_deploys(serviceId, limit)
list_logs(resource: ["<id>"], level: ["error"])
get_metrics(resourceId, metricTypes: [...])
# Workspace
get_selected_workspace()
list_workspaces()
```
### CLI Commands
```bash
# Validate Blueprint
render blueprints validate
# Check workspace
render workspace current -o json
render workspace set
# List services
render services -o json
# View deployment logs
render logs -r <service-id> -o json
# Create deployment
render deploys create <service-id> --wait
```
### Templates by Framework
- Node.js Express: [../assets/node-express.yaml](../assets/node-express.yaml)
- Next.js + Postgres: [../assets/nextjs-postgres.yaml](../assets/nextjs-postgres.yaml)
- Django + Worker: [../assets/python-django.yaml](../assets/python-django.yaml)
- Static Site: [../assets/static-site.yaml](../assets/static-site.yaml)
- Go API: [../assets/go-api.yaml](../assets/go-api.yaml)
- Docker: [../assets/docker.yaml](../assets/docker.yaml)
### Documentation
- Full Blueprint specification: [blueprint-spec.md](blueprint-spec.md)
- Service types explained: [service-types.md](service-types.md)
- Runtime options: [runtimes.md](runtimes.md)
- Configuration guide: [configuration-guide.md](configuration-guide.md)
## Common Issues
**Issue:** Deployment fails with port binding error
**Solution:** Ensure app binds to `0.0.0.0:$PORT` (see Port Binding section above)
---
**Issue:** Build hangs or times out
**Solution:** Use non-interactive build commands (see Build Commands section above)
---
**Issue:** Missing environment variables in Dashboard
**Solution:** All env vars must be declared in render.yaml. Add missing vars with `sync: false` for secrets.
---
**Issue:** Database connection fails
**Solution:** Use `fromDatabase` references for internal connection strings.
---
**Issue:** Static site shows 404 for routes
**Solution:** Add rewrite rules to render.yaml for SPA routing:
```yaml
routes:
- type: rewrite
source: /*
destination: /index.html
```
For more detailed troubleshooting, see the debug skill or [configuration-guide.md](configuration-guide.md).
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: 197k | 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 |