Skip to content

feat(deploy): Railway support with PORT-aware serve entrypoint#55

Draft
Gsbreddy wants to merge 1 commit intomainfrom
cursor/railway-deploy-3ca2
Draft

feat(deploy): Railway support with PORT-aware serve entrypoint#55
Gsbreddy wants to merge 1 commit intomainfrom
cursor/railway-deploy-3ca2

Conversation

@Gsbreddy
Copy link
Copy Markdown
Collaborator

@Gsbreddy Gsbreddy commented May 4, 2026

Summary

Adds Railway deployment guidance and examples/deploy/railway.toml (Dockerfile builder, /health check).

Important: Railway sets PORT at runtime. entrypoint.sh now runs flightdeck serve --port "${PORT:-8765}" so the container listens on Railway’s assigned port while local Compose keeps default 8765. Dockerfile HEALTHCHECK probes PORT as well.

Docs cover: verify current Railway pricing (free tier wording changes), public domain, optional /workspace volume for SQLite persistence, FLIGHTDECK_LOCAL_API_TOKEN, and subdirectory deploy (service root examples/deploy or RAILWAY_DOCKERFILE_PATH).

Verification

Shell changes only in deploy image path; existing Compose behavior unchanged (no PORT → 8765).

Open in Web Open in Cursor 

Railway injects PORT at runtime; entrypoint binds flightdeck serve to
PORT with 8765 fallback for local Compose. Dockerfile healthcheck follows
PORT. Add railway.toml (Dockerfile builder, /health check) and README
section with pricing caveat, volume, and token guidance.

Co-authored-by: Gottam Sai Bharath <Gsbreddy@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants