Running the Stack Locally

Prerequisites

You’ll need a recent Bun and Docker. Copy .env.example to .env and fill in the paths for your author manifest and services.

Bring it up

The full stack — Postgres, Redis, the author server, and the title router — comes up with one command:

docker compose up –build

Once it’s healthy, point the web client at your local router and load a title from your manifest to confirm everything is wired together.

Debugging a title

When a game misbehaves, run it in isolation against the engine CLI before suspecting the stack. Most issues are in the title script, not the infrastructure — replay the event log to see exactly where the scene diverged.

Placeholder guide — the real version will walk through manifest setup, common compose failures, and the transcript log in detail.