-
Notifications
You must be signed in to change notification settings - Fork 5
Expand file tree
/
Copy pathrailway.toml
More file actions
32 lines (27 loc) · 1.43 KB
/
Copy pathrailway.toml
File metadata and controls
32 lines (27 loc) · 1.43 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
# ── Railway Deployment Config ─────────────────────────────────────────
# Docs: https://docs.railway.com/config
#
# Railway auto-detects the Dockerfile in the repo root, so [build] is
# optional. We just set startCommand to run the Telegram bot (the default
# Dockerfile CMD starts the API server under the process supervisor instead).
# ──────────────────────────────────────────────────────────────────────
[build]
# Dockerfile is auto-detected — no build command needed.
# If you prefer Nixpacks instead of Docker, uncomment:
# builder = "nixpacks"
# buildCommand = "bun install"
[deploy]
# Default: run the Telegram bot (controlled from your phone 24/7)
startCommand = "bun run index.ts telegram"
# To run the API server with the process supervisor (auto-restart on crash):
# startCommand = "bun run index.ts serve --supervisor"
#
# To run the API server directly (no supervisor watchdog):
# startCommand = "bun run index.ts serve"
restartPolicyType = "on-failure"
restartPolicyMaxRetries = 10
# Health check against the API server (runs in both Telegram and serve modes
# because the API health endpoint is always available)
[deploy.healthcheck]
path = "/api/v1/health"
port = 8080