Deployment Runbook
Stand up Prism Refactory without guessing through first boot.
This is the operator path for a fresh Prism Stack deployment: Railway template, site initialization, Discord setup, GitHub access, and the first end-to-end smoke checks.
1. Deploy the template
Start from the Railway template. This provisions the site, Prism Memory, Codex runtime, Discord adapter, and scheduled jobs with the current default topology.
2. Confirm site initialization
Log into /admin with the template default admin password and verify the board loads. On a healthy first boot, /api/health should report appliedMigrations: 5.
3. Configure the Discord bot
In the Discord developer portal, install the bot with bot and applications.commands scopes. Enable Message Content Intent. For voice recording, ensure Connect, Speak, Use Voice Activity, View Channel, Send Messages, Send Messages in Threads, Create Public Threads, and Read Message History.
4. Point internal services at private URLs
Use Railway private domains for service-to-service calls. In particular, keep discord-adapter talking to Prism Memory, Codex runtime, and site over internal URLs rather than public edge domains.
5. Add a target repository
Create a fine-grained GitHub token with metadata read and contents, issues, and pull requests read/write. The token owner must also have effective write access to the target repository, either directly or through team access.
6. Run the first smoke pass
Test admin login, create a change request, verify the bot responds to ping, run /prism-health, and complete one recording flow if you plan to use meeting capture.
Required Env Checks
- SITE_USE_LOCAL_APP_API=true on site
- PRISM_AGENT_DATA_ROOT=/data on site
- NEXT_PUBLIC_API_BASE_URL points to the site public domain
- APP_API_BASE_URL on codex-runtime and discord-adapter points to site internal URL
- PRISM_API_BASE on discord-adapter points to prism-memory internal URL
- VOICE_DAVE_ENCRYPTION=true unless you have a proven reason to change it
First Smoke Checks
- Admin login works with the configured password
- The board loads instead of returning admin API errors
- A CR can clone, branch, push, and open a PR against the target repo
- The bot returns pong on ping
- /prism-health reports ready state and current voice permissions
- A recording session produces transcript and summary links in Discord
Next
Once the stack is healthy, move into real workflows.
Link your target repository, run the first change request, and start using Discord and meeting capture against live community activity rather than a blank template.