a year ago
Services with public network are supposed to have this "auto-generated" variable in order to easily refernece their URLs from other deployments. Unfortunately, whether or not this appears when creating a new service (especially when duplicating a service that has a public URL) seems to be hit-or-miss.
As you can see in the screenshots, I have a deployed service with an assigned public URL, but it doesn't have the RAILWAY_PUBLIC_DOMAIN varialbe. Other services even in the same environment that share identical configuration do.
Am I missing something?
1 Replies
a year ago
i tried making a reproducible example, and could not reproduce, this is what I see right after deploying the template
a year ago
the template for referance -
a year ago
odd, so we both can't reproduce
a year ago
I've had this happen to me too, it's rare that it happens though so I don't think it can be reliably reproduced
When it does happen I just hardcode the URL into my service variables
a year ago
unfortunately we aren't able to fix it if we can't reproduce it
a year ago
that's fair, just giving my 2 cents
a year ago
Can confirm this flake (1-in-20 new PR environments perhaps?). Not certain, but I have the sense that attempting to activate/use the environment via the CLI very soon after environment creation might trigger the issue, but this could be a false pattern.
a year ago
If you can provide fully reproducible steps that would be much appreciated, as it stands there's nothing for us to action on.
No, deployed from a GH repo, but I'm also sure that I've seen this before with some Redis template
a year ago
Redis doesn't have a public domain
a year ago
it's not a website
right, but isn't there supposed to be an automatic variable for the "proxy domain" of public networking as well?
a year ago
yes there is one available, don't think it shows up in the recommend variables as there's over a dozen, we don't show them all
alright well forget about that. that was a while ago and I'm probably not remembering the details correctly.
Unfortunately it's flaky for me as well, I just tried deploying the same exact thing I did in my initial screenshots again and didn't have the problem. Would it make sense to post service IDs here when I see it again? Maybe there's some hidden pattern.
a year ago
yep if you see it again feel free to bring it back up!