41cdc7cd-f1a1-4445-b931-699b4b4215e4

Any help would be awesome thx 🙂

Hello?

🙂

hello, please note that the railway team doesn't guarantee response times for hobby users, responses from the team for hobby users are offered at a best effort basis.

Thanks Brody. I did notice a number of other hobby users receving support quickly with more recent posts…

Is this a low priority item for your team?

I think I've already replied to your support ticket on our central station?

Ah well I didn't see that.. I'm new here, not sure where the central station is?

I found central station… well I don't seem to have anything there in inbox or threads. If you have the URL to your reply, I'd be happy to have a look.

apologies, I may be thinking of a similar thread from a different user

no problem.

I set up a thread on Central Station as well:
https://station.railway.com/questions/monorepo-deployment-issues-9d696d5a

we would ask you not to create duplicate posts

Sure, no problem. Like I said I'm new here, just trying to figure out based on your comments where the right place to post for help is.

Hi Brody 👋 I upgraded to a Pro plan. Looking forward to resolving this. Cheers.

you shouldnt need a watch path set when you have a root directory set, have you tried without watch paths?

Morning 👋 , just tested it out:

• Removed all watch paths.

• Changed the readme in /queue-service and pushed code to my dev branch. All the services I have on Railway then restarted.

FYI I had the same issue with watch paths because I have a mono repo with a few services with separate dockerfiles etc..

i followed the docs example for watch paths where the paths are all prefixed with a / as if that represents the root of the repo… that did not work, and all the services kept getting rebuilt every time I pushed to the repo.

I fixed it for my case by making the watch paths relative.. ie. not prefixed with a /

so i have my watch paths as:

libs/xx
libs/yyy
package.json
yarn.lock

this seems to work flawlessy… now I don't know if I was doing something wrong, or if the docs were just wrong, but maybe this will work for you as well.

I'll give it a shot, thanks Arnór

I .. I think that solved it. Will verify with another repo change. I was following the docs examples as well with the leading /

Works on 3 separate repos for the project. Only those repos redeploy! I salute you @Arnór <:HappySeal:1278652191791386698>

This is solved.

Amazing! Much appreciated @Arnór <:salute:1137099685417451530>

Thanks for helping

!s