parththakkar106andClaude Fable 5
466d7bc0e4
Phases: public repo & Docker (7), guest-first optional accounts (8), production hardening (9), Render deploy (10). Confirmed decisions and per-phase open questions recorded in each file. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KFsGHju9szibJJa2YJcdbg
2.2 KiB
2.2 KiB
Phase 10 — Deploy & publish
Goal: the app live on Render at a public URL, linked from resume/website alongside the GitHub repo.
Decisions (confirmed)
| Question | Answer |
|---|---|
| Platform | Render |
| Domain | Platform URL is fine (e.g. ai-dnd.onrender.com); custom domain can be added later anytime |
Ask before implementing: Render tier (free-with-sleep vs ~$7/mo always-on — depends on the Phase 9 database decision), and the exact service name (it becomes the public URL).
Deploy
render.yamlblueprint: web service from the Dockerfile, env vars (SECRET_KEY generated, demo-key vars,MULTI_USER=true), health check endpoint, plus disk or managed Postgres per the Phase 9 decision.- Set up the Render service, connect the GitHub repo, auto-deploy on push to
main. - Seed production with 2–3 good demo scenarios (public/starter scenarios from Phase 8) so first-time visitors have something great to click immediately.
- Smoke test the live URL: guest play on demo key, register, BYOK flow, scripting, memory bank, Insights — from a device/network that isn't yours.
- Free-tier note: if on free tier, first request after idle takes ~30–60s to wake — add a friendly loading state or accept it (revisit tier if it feels bad).
Post-launch guardrails
- Watch demo-key spend/usage for the first days (OpenRouter dashboard); confirm caps hold.
- Set up uptime monitoring (free: UptimeRobot or similar) — optional.
- Error visibility: Render logs are enough for v1; note how to pull them.
Resume / website
- README: add the live-demo link + "Try it" section at the top.
- 2–3 sentence project blurb for resume/website (stack, the interesting hard parts: AI Dungeon-compatible JS scripting sandbox, embedding-based memory bank, prompt transparency, guest-first optional auth).
- Later pass (deferred from Phase 7): screenshots/demo GIF for README and website card.
Exit criteria
A recruiter clicks one link on your resume, lands on the live app, plays three turns of a demo scenario as a guest without configuring anything, and can find the GitHub repo from the page.