3 days ago
been trying to set a meeting with railway themselves to discuss moving forward, best practices and a better way to approach this codebase( currently its bloated)
also seeing how docker will work. so if there is anyone who is willing to have a conversation with me, ( paid if need be) i would appreciate it .
ps: current setup has the entire code uploaded for each service but only select folders being run
0 Replies
2 days ago
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.
14 hours ago
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.
12 hours ago
hey, running NestJS + NextJS on Railway with turborepo too
12 hours ago
so far we're using Railway's auto build system and it's going great, Dockerfiles were a mess to maintain
12 hours ago
if you have any questions, just shoot them here, no need to pay anyone