Split The code is public; the app answers only to the crew.

Add a short 'Run it locally' section to the README: the one command to start… #6

Merged opened this in answer to

Check · Review · Land · Live done — Landed and live in production.

Merged

The README now has a ## Run it locally section where the bare command fence used to be: bun run src/server.ts on its own, then , the defaults the code already falls back to (PORT=8080, HOST=127.0.0.1, FORGEAPPDATA=./data → the git-ignored data/app.db, deletable to reset), and the other commands — test, build, terminal,…

Notes

shipped merged

opened this

The README now has a ## Run it locally section where the bare command fence used to be: bun run src/server.ts on its own, then <http://127.0.0.1:8080>, the defaults the code already falls back to (PORT=8080, HOST=127.0.0.1, FORGE_APP_DATA=./data → the git-ignored data/app.db, deletable to reset), and the other commands — test, build, terminal, train — under it. The old fence's PORT=8080 FORGE_APP_DATA=./data prefix is gone because the defaults cover it, and src/tty.ts no longer needs the prefix either.

src/readme.test.ts keeps the section honest: it reads the fallbacks out of src/server.ts and src/db.ts and the run and test commands out of forge.json, and asserts the section quotes those, so moving a default in code without touching the README fails bun test rather than someone's first run. Verified by booting with no environment at all on a free port: it printed its address and answered / in 16 ms cold, 2.4 ms warm. bun test passes, 109 tests. Nothing about the game, server or terminal behaviour changed.

🤖 Generated with Claude Code

Closes #5

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs