5a0da8a8-b005-4319-b717-ff4346eaeab2

sorry i thought this happened automatically when i connect to railway

Hello,

Apologies, but we (the Railway team) cannot offer support for your application's architecture, but I would be happy to answer any Railway platform or product specific questions.

Is there a way for us to connect on the discord with some pro?

Asking here is your best bet, but please provide more details. The only information you’ve provided so far is that your codebase is bloated

the current approach that i just minimally followed ( as a monorepo using turbo) is uploading the whole code base on each of the microservices and only running the packages and microservices.
my next step should be docker
but im lacking proper theoretical approach to the dockerfiles. especially with a nestjs microservice.
at teh current moment any sense of direction will be welcome.
im willing to pay an hourly rate for whoever is available as well.

hey, running NestJS + NextJS on Railway with turborepo too

so far we're using Railway's auto build system and it's going great, Dockerfiles were a mess to maintain

if you have any questions, just shoot them here, no need to pay anyone

thank you @ThallesComH
was wondering how you had railway run your monorepo?
i have 3 microservices with an api gateway controller.
the issue is in every instance of hte microservice i have to upload the whole repo but only run the parts that work.
ended up creating a railway script for every repo
"build:railway": "cd ../../.. && pnpm run build --filter=@repo/shared && cd apps/backend/api-gateway-service && nest build",
is there a lighter approach you might consider ?

@ThallesComH pinging for visibility ^

Hey, earlier we were running each separate section instead of uploading the whole repo with a custom Dockerfile. However, maintaining that Dockerfile with all the environment variables wasn't worth the effort. So we decided to let Railway figure it out, which means they'll upload the entire repo on all services but will run only the relevant parts. For now, we're not experiencing any problems.

thanks, got busy and forgot to reply

No worries, thread has been bountied for you 😉

for commands, these are the ones we're using, kinda the same as you.

the thread has a bounty? didn't notice it

now it has 😉

It worked. Thank you

Great! I’ve marked this thread as solved, could you please mark Thaless’ answer as the accepted answer so the bounty can be awarded?

https://station.railway.com/questions/connectivity-considerations-nestjs-next-483f64cb

pinging for visibility @Grimmjoww231

I'm running NextJs on railway. I want to pre-build it in my Github Actions, such that it activates without needing to build, after I run a database migration

It seems like the ideal approach is to have a prebuilt docker image I give to Railway that I create in the build step.

But this requires managing NextJs deployment via a custom dockerfile rather than Railway's prebuilt one. Any tradeoffs I should be wary of?

hello, please open your own thread. This thread has been resolved and closed for another user’s question