Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kuest.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Prerequisites

​
Deploy flow

1

Create a web service

In Railway, create a new service from your GitHub repository.
2

Point Railway to the config file

Because railway.json is not at repository root, set this in Railway service settings:
  • Config file path: /infra/railway/railway.json
With that set, Railway reads build and deploy options from the file, including:
  • Builder: DOCKERFILE
  • Dockerfile path: infra/docker/Dockerfile
  • Pre-deploy command: npm run db:push
3

Set environment variables and secrets

Add the shared values from Environment Variables, then set exactly one storage profile from Manual Installation Overview.
4

Generate a public domain and set SITE_URL

In Networking, generate or attach a domain and set SITE_URL to that final HTTPS URL.
5

Deploy and verify migrations

Trigger a deployment and confirm the pre-deploy step runs npm run db:push successfully in the Railway deploy logs before opening production traffic.

​
Scheduler

Railway deployment does not replace the sync scheduler requirement. If you are not using Supabase mode, configure external jobs following Scheduled Jobs.
Keep the app listening on PORT in Railway so health checks can pass consistently.