Railway Default Variables Working on Some Templates, but not others
Example
${{RAILWAY_TCP_PROXY_PORT}}18 Replies
Project ID:
N/Aworking
not working
ProjectID:
82ad1aad-b015-417a-bd35-6bbc9aabeef0
But ive noticed this on spinning up several fresh projects from templates.I can't speak for all templates, but most of my templates come without the proxy on the database enabled, thus the port would be an empty string
I don't know if you are deploying one of my templates, but all templates I have that also have databases without the proxy have notes in their overview explaining this, example
https://railway.app/template/umami-analytics
very useful information! much appreciated
so haha are you using one of my templates
ah I see a
PGPORT_PRIVATE variable, thats only on databases I ship or helped to ship with templates
so if you ever have any questions about such templates you know where to find me!its a pattern i have seen over the last 4/8?? weeks across many templates, that didn't previously have this default behavior.
yep besides my templates, I've helped friends update their templates and I've even been given a couple of templates to update in such a way
sorry alex, we've already covered why the variables are missing
no one reads anymore
including myself
well we know why they are missing, but why I've done this is because if you use the public tcp proxy your database is subject to egress fees, exclusively using the private network to connect to the database means zero egress fees on the database service
yea
honestly I want something as simple as railway for doing local deployments of stuff
I'd love to be able to spin up a docker container + volume for a brand-new postgres with a single command lolol
you know, i saw the egress update,
but it kinda fell into the background noise for me.
seeing as im (today) connecting two railway services, you mighta just helped me dodge a bullet. 
that is one of the main reasons I started bugging my friends to update their templates
docker compose you silly
low skill!!!