Render Tutorials
Learn Blueprints by shipping a live app

Deploy once (Dashboard or MCP)

⏱ 14 min

Pick one path. Do not run both on the same fork in this session.

Same render.yaml on your fork
        ├─→ Path A: Dashboard (default)
        └─→ Path B: MCP + RENDER_API_KEY (optional)

Path A: Dashboard (default)

Docs: Blueprints setup

  1. Open the Dashboard Go to dashboard.render.com. Select the Render Atlanta workshop workspace when your invite is ready.
  2. Start a Blueprint Click + New → Blueprint.
  3. Connect your fork Find YOUR_GITHUB_USERNAME/firstdeploy-starter and click Connect. Connect GitHub if asked.
  4. Name and branch Name the Blueprint instance. Keep branch main. Blueprint Path: render.yaml.
  5. Review and deploy Confirm the web service in the change list. Click Deploy Blueprint (the button may say Apply).
  6. Open the new web service From the Blueprint progress page (or the service list), open the web service that was created.

Path B: MCP (optional)

Only if you finished Install skills and (optional) MCP section 3.

Prompt your agent

I already have a render.yaml for a single free web service, and RENDER_API_KEY is set.
Use the render-mcp / render-deploy skills to deploy this Blueprint via MCP
into my current Render workspace. Do not also walk me through a second Dashboard
Blueprint apply. When done, give me the .onrender.com URL and how to confirm Live.

When the agent finishes, open the service it created in the Dashboard.

Where to check the deploy

Everything below is in the Dashboard, on your web service page (not only in the agent chat).

WhereWhat you look for
EventsHigh-level timeline: deploy started, succeeded, failed
DeploysEach deploy row: commit, status (Live, Build failed, …), timestamp. Click a row for build logs
LogsRuntime output after the app starts (Service Card … on http://0.0.0.0:…)
MetricsCPU/memory after traffic (optional today)
Header URLYour *.onrender.com link. Open it in a browser

Checklist after deploy

  1. Latest deploy status is Live (Deploys tab)
  2. Open the public URL from the service header
  3. Title matches SERVICE_TITLE from your Blueprint
  4. Runtime badge matches your track (TypeScript or Python)
  5. Click Ping; the counter increases
  6. Optional: open /health → ok
Where do you confirm a deploy reached Live?

Troubleshooting

SymptomFix
Repo missing in Blueprint listConnect the GitHub App; grant access to the fork
Build cannot find filesConfirm rootDir matches your track
Status stuck / failedOpen the failed deploy → read the build log
App never opens portsBind 0.0.0.0 and read PORT (starters already do)
MCP 401Recreate RENDER_API_KEY; restart the editor

What you learned

  • One deploy path only
  • Deploys + Events + Logs live on the service page
  • Next: where to go after this workshop