feat: add Railway deployment — blueprint, frontend Dockerfile, guide - #36
Merged
Conversation
- railway.toml — defines squadsync-db (Postgres 16), squadsync-api (FastAPI), squadsync-web (Next.js) services with build configs and environment variables - frontend/Dockerfile — multi-stage standalone Next.js production build - frontend/next.config.ts — set output: 'standalone' for Docker deployment - RAILWAY.md — step-by-step deploy guide, env reference, architecture diagram, gotchas
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
comwanga
marked this pull request as ready for review
August 8, 2026 20:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Railway deployment setup so SquadSync can run entirely on one platform (frontend + backend + Postgres) without splitting across Vercel and Render.
Files
railway.tomlsquadsync-db(Postgres 16),squadsync-api(FastAPI viabackend/Dockerfile),squadsync-web(Next.js viafrontend/Dockerfile). All env vars templated with Railway secrets.frontend/DockerfileNEXT_PUBLIC_API_URLat build time) → runner on port 3000 as non-root userfrontend/next.config.tsoutput: "standalone"(required for the Docker build, silently ignored by Vercel)RAILWAY.mdHow to deploy
railway.toml→ provisions DB + both servicesRAILWAY.md)NEXT_PUBLIC_API_URLis setExisting Vercel + Render deployment is unaffected by these changes.