Backend deployment prep for Railway
From the PR description
Summary: Prepares backend env documentation for Railway deployment readiness. The backend already uses npm commands, process.env.PORT, FRONTEND_URL CORS, unauthenticated /health, and nixpacks LibreOffice. Added NEXT_PUBLIC_SUPABASE_URL to backend/.env.example because backend/src/routes/workflows.ts still reads it. Validation: cd backend && npm ci passed; npm run build passed; npm start was launched with placeholder env on PORT=43019 and GET /health returned {ok:true}. Railway settings: root directory backend; install npm install; build npm run build; start npm start; health check /health; Node 22.x; Nixpacks uses backend/nixpacks.toml with libreoffice.
Our analysis
Prep backend env for Railway deployment — read the full analysis →
Think the analysis missed something the PR description covers?
Commits in this PR (1)
| SHA | Subject | Author | Date | |
|---|---|---|---|---|
d872d0fc | prep backend env for railway deploy | SONOMOS | 2026-05-07 | ↗ GitHub |
Capture this PR into my fork
Download a Markdown prompt that tells Claude how to port every
commit in this PR into your working tree. Run it via
claude -p < capture-pull-19.md from
inside the repo you want the changes in.