HaloStack Docs

HaloStack deploys to Railway as code. The topology lives in .railway/railway.ts; environment variables, init steps, and preview helpers live under infra/railway.

Topology

Railway runs five app services and two data plugins:

Unit	Railway shape
`api`	HTTP service with `/health` and a pre-deploy migration command
`web`	TanStack Start SSR service, serverless sleep enabled
`docs`	Fumadocs/TanStack Start service, serverless sleep enabled
`landing`	Static Astro service served by a small HTTP server
`worker`	Cron one-shot service with `JOB_NAME` in the start command
Postgres	Railway plugin, injected as `DATABASE_URL`; persistent volume at `/var/lib/postgresql/data`
Redis	Railway plugin, injected as `REDIS_URL`; persistent volume at `/bitnami`

Object storage stays external on Cloudflare R2. DNS stays manual in Cloudflare. Production env sync verifies these data volumes and fails if they are missing.

Commands

bun run railway:iac
bun run railway:env --dry-run
bun run railway:env
bun run railway:init
bun run railway:env:up staging
bun run railway:env:down staging

Production requires a custom ROOT_DOMAIN. Non-production environments can omit it and run in preview mode on Railway *.up.railway.app domains, with AI/email optional and the seeded demo login available.

See infra/railway/README.md for the full runbook.