foolish-bandit wires Gary up for hosted deployment

The fork now ships a real playbook for putting the backend on commodity hosting providers.

infrastructure

foolish-bandit has added proper deployment documentation for the backend, covering install and build steps, the full list of required and secret environment variables, and host-specific instructions for Railway and Render - two popular pay-as-you-go hosting services that take a code repo and run it for you. It also covers how to point the frontend at the deployed backend and a smoke test to confirm everything came up clean.

A stray lockfile that was tripping up the hosts' auto-detection has been removed, and a small follow-up patched a missing environment variable that Railway needed. Taken together, this is the fork moving from "runs on my laptop" to "runs somewhere a customer could reach."

So what Anyone evaluating Mike forks as candidates for a hosted demo or pilot should note that foolish-bandit has already paid the deployment tax - the documentation alone is a useful shortcut.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

6 commits from foolish-bandit/gary, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`d2245301`	Merge pull request #4 from foolish-bandit/claude/prepare-backend-deployment-2J0Le	Zack Brenner	2026-05-07	↗ GitHub
Document backend deployment on Railway/Render
`014f57ae`	Merge pull request #5 from foolish-bandit/claude/remove-backend-bun-lockfile	Zack Brenner	2026-05-07	↗ GitHub
Remove backend/bun.lock so hosts use npm
`24be1632`	Document backend deployment on Railway/Render	Claude	2026-05-07	↗ GitHub
commit body Adds backend/DEPLOY.md with install/build/start commands, the full required-vs-secret env var matrix, host-specific (Railway, Render) steps, frontend wire-up via NEXT_PUBLIC_API_BASE_URL, and a post-deploy smoke test. Links it from the root README so it is discoverable next to the existing frontend/Workers section. https://claude.ai/code/session_019pRkhcGDRKQWHjzAnV5yCL
`eac38d95`	Remove backend/bun.lock so hosts use npm	Claude	2026-05-07	↗ GitHub
commit body backend/package-lock.json is the active lockfile and the README + DEPLOY docs prescribe npm. A stale bun.lock can mislead build detectors (Railway Nixpacks, Cloudflare, Render) into provisioning Bun, which is exactly the trap the frontend just hit. https://claude.ai/code/session_019pRkhcGDRKQWHjzAnV5yCL
`d872d0fc`	prep backend env for railway deploy	SONOMOS	2026-05-07	↗ GitHub
`6404ba39`	Merge pull request #19 from foolish-bandit/codex/pr-19-railway-backend-deployment-prep	Zack Brenner	2026-05-07	↗ GitHub
Backend deployment prep for Railway

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-157.md from inside the repo you want the changes in.

⬇ Download capture-thread-157.md