9 months ago
We will be working on a seamless monorepo configuration and deployment flow so you no longer need to go through multiple hoops to get this going.
We currently do not have an explicit flow for handling monorepo configuration and you should be able to deploy all your monorepo services in the time it takes to deploy one 
To deliver that Railway delight at every step 
0 Threads mention this feature
3 Replies
Status changed to Planned chandrika • 9 months ago
4 months ago
Probably the slowest aspect of deploying a monorepo is rebuilding same image N times. I switched to building images in CI, and deploying them directly to get around this issue.
It probably would make sense to have a Docker image registry exposed as part of the Railway platform. Then I build and push directly to Railway. Currently, I build in CI, push to the Github image repo, then run a separate CI action using the Railway graphql API to redeploy using the new image.
4 months ago
It is relatively quick to deploy a monorepo one time, then change root door -> duplicate -> change root dir.
This works great for small monorepos, but full support would be nice.
3 months ago
I'd just like to flag that it'd be great if functions were treated as first-class citizens as part of more robust monorepo support. There's much feedback about functions in this thread, including several requests for managing function definitions via git.