hebertzhu Render Deploy
Intent
- Use for Render deployment planning,
render.yamlauthoring, and Git-backed Blueprint handoff with a reproducible deploy path.
Default operating pattern
- Confirm the repository already has a pushed Git remote before designing the deploy flow; if not, stop and ask the user to push the repo first.
- Analyze the app shape and decide whether the Blueprint should include a web service, static site, worker, cron job, or supporting datastore.
- Create or update a minimal
render.yamlthat keeps secrets unresolved and documents the actual build, start, and runtime requirements. - If the Render CLI is available, run
render blueprints validate; otherwise, call out the missing validation step clearly instead of pretending it was checked. - Convert the Git remote to an HTTPS URL if needed, then build the Blueprint deeplink as
https://dashboard.render.com/blueprint/new?repo=<HTTPS_REPO_URL>. - Return the deeplink and the next manual steps: push
render.yaml, fill secrets, apply the Blueprint, and monitor the first deploy in Render.
Pack fit
- Included in:
deploy-ops - Favor the reproducible Blueprint path over host-specific automation or private deployment glue.
Boundary
- Do not continue with a Blueprint flow if the repository is not pushed to a supported Git host.
- Do not assume image-backed direct deploys, MCP automation, or pre-created infrastructure unless the current environment already exposes them.