CiaranSweet
Not skipping build/deployment for changes outside root directory
I also noticed this, wondered if I had done something wrong.. a workaround I found was to use the Watch Paths https://docs.railway.app/guides/build-configuration#configure-watch-paths
But this seems like it shouldn't be needed after setting the root directory of each service. So very interested in what the solution is!
10 replies
Private networking with Railway generated ports
Okay, so a little progress:
If I hardcode the port to what I see in my backends logs (from the port Railway generated), I get a connection
So I guess the real question is - How the heck do I get that port without log diving 😄
87 replies
Private networking with Railway generated ports
This is what I have right now, Railway setup the port for backend, so I assume I'll be able to access that value.
This resolves to
'http://[backend.railway.internal]:'
If I remove the []
from my ENV (Even though that's not what I should do), it resolves to the actual ipv6 address.
Either way I do it, PORT
Is empty anyway 🥲87 replies