chore: point Deploy to Render URLs at fastapi/full-stack-fastapi-template

For upstream PR — if merged, the Blueprint lives in fastapi/..., so the
deploy button and render.yaml repo: field should point there.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Ho1yShif

README.md

@@ -6,7 +6,7 @@
 
 ## Deploy to Render
 
-[![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy?repo=https://github.com/render-examples/full-stack-fastapi-template)
+[![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy?repo=https://github.com/fastapi/full-stack-fastapi-template)
 
 One click provisions the full stack on [Render](https://render.com) using the [`render.yaml`](./render.yaml) Blueprint at the repo root: a Dockerized FastAPI web service, a Vite/Bun static site for the frontend, a managed Postgres database, and a shared `fastapi-env` environment-variable group that both services pull from.
 

render.yaml

@@ -23,7 +23,7 @@ projects:
             name: fastapi-backend
             runtime: docker
             plan: free
-            repo: https://github.com/render-examples/full-stack-fastapi-template
+            repo: https://github.com/fastapi/full-stack-fastapi-template
             branch: main
             autoDeploy: true
             dockerfilePath: ./backend/Dockerfile
@@ -76,7 +76,7 @@ projects:
           - type: web
             name: fastapi-frontend
             runtime: static
-            repo: https://github.com/render-examples/full-stack-fastapi-template
+            repo: https://github.com/fastapi/full-stack-fastapi-template
             branch: main
             autoDeploy: true
             buildCommand: bun install --frozen-lockfile && bun run --filter frontend build