2 years ago
This says it will create egress fees even tho it's linked via variables with the backend. How do I fix this?
16 Replies
2 years ago
it'll only use egress fees if you actually use it, you don't have to make use of it
But it says to change to railways private domain instead? But the service uses the internal postgres env variables references already so isn't that private already?
2 years ago
But it says to change to railways private domain instead?
What you're seeing there is an automated warning based on the content of the variable, Railway's seeing that the variable references a public database url and so it gave that warning, but the variable is only actually there for you to use so if you're not using it then no ones using it so it's completely fine
But the service uses the internal postgres env variables references already so isn't that private already?
if you're using the DATABASE_URL variable and not the DATABASE_PUBLIC_URL then you're using the private network
i got both lol, should I remove public url?
2 years ago
what service is that from?
2 years ago
you don't need to remove that URL then
2 years ago
just don't use it
2 years ago
going to reiterate what fragly has said, please do not modify variables on your database
2 years ago
If you want to completely remove public access to your database, remove the TCP proxy domain instead.
Yeah but now I think about it.. maybe it's better leaving that there just in case I do want to be able to query on it manually via remote.
Status changed to Solved dev • over 1 year ago