3 days ago
Two things required to have first-class support for static sites.
- builds
- CDN
now that Railway has both in house, how about providing first-class support for static sites.
I have many projects which are deployed like this
- frontend on vercel + backend on railway
- frontend on github pages + backend on railway
- frontend on netlify + backend on railway
It will be great if I can finally have a monorepo with backend and frontend code both and they both can be deployed to Railway.
Yes the backend can just proxy the entire frontend as a static site internally (Go/Express/Rails everyone has that) but it'd be nice for Railway to support building and deploying static sites directly from a repo as first-class primitive.
0 Threads mention this feature
2 Replies
3 days ago
What type of static site are you looking to deploy that isn't supported right now? We do auto detect HTML and automatically serve it. We are definitely looking to improve our static site support, but wondering what specifically you are trying to deploy that isn't great.
jr
What type of static site are you looking to deploy that isn't supported right now? We do auto detect HTML and automatically serve it. We are definitely looking to improve our static site support, but wondering what specifically you are trying to deploy that isn't great.
15 hours ago
This is an example, frontend on github pages + backend on Railway
https://github.com/championswimmer/datacenter-tycoon
This is an example of a Vue app that deploys to Netlify with literally 0 config (open Netlify, select repo, deploy)
https://github.com/championswimmer/app.midpoint.place
I know on Railway I can do SPA with Caddy as a service. But for frontends, I do not want to deal the 'service' primitive. I just want to see build logs for the build, and then after that, it should be just hosted (i don't care if Railway uses caddy, or whatever way it puts the frontend on the CDN)