railway connect via CLI - private network default?
Hi all,
I think I've "resolved" this but a general question. I've used railway in the past and it's been straightforward. I was excited to see the private networks added.
Whenever I do something like
railway connect Postgres though, the defaults point it at the internal host (postgres.railway.internal) and it throws an error. I can of course change the url, but given that this is the CLI and I understand that's only accessible via the public URL, I'm curious about this default.
1. Am I thinking about this correctly, or missing something obvious?
2. Is railway still the best option for my use case? I just want a postgres container but don't need all the baked in frameworks (e.g., not using Prisma or Drizzle, or here even a web app). The current piece of work is ETL, and I'll use the result of that for an API.
Thank you and sorry for the noob questions! This is generic and not specific to a particular project.4 Replies
Project ID:
N/AN/A
all the database templates where recently updated so they use the private host and port by default to try and prevent users from using the public host and port when running on railway and racking up egress.
the cli just hasn't been updated to accommodate this change yet.
we have a ticket open for this and i will update you when theres changes in regards to this issue being solved
Solution
hey, this has now been fixed!