6 days ago
Hi there,
I'm deploying a mono repo project that has a react/vite FE and python backend. I chose to build these in a mono repo with two distinct paths /apps/web and /apps/api.
I have two different services up and I have had a shocking amount of trouble deploying the api container. I couldn't get it to respect the nested railway.toml specific to the api containers. The start command was being read from the root railway.toml, even though I explicity specified the root of the project to be apps/api with a corresponding apps/api/railway.toml. I manually updated the start command, deployed, and then went back and checking the start command in settings and it hadn't updated. Just to name a few issues.
Frankly I'm a bit surprised it has been this hard to get this deployed when there is no free tier. The existing functionality being buggy, plus really no IAC support has me asking the question of whether or not I should just take this all to AWS. It really pains to even THINK about doing that but lack of support and buggy feature set (for features that are supported) is quite frustrating.
I'm happy to hear any feedback on my project setup but right now this is a less than ideal dev ex.
Thank you,
Mike
0 Threads mention this feature
0 Replies