yep, that would explain. railway shell doesn't connect you to our network but only creates a shell with the env from your selected service.

Your options here would be to change the way you run migrations and specify the remote (public) database url locally, or make it so migrations run in your start command, before bringing the service up, which is a fairly common practice.

Brilliant. I've updated my Dockerfile CMD ["sh", "-c", "node ace migration:run --force && node ./bin/server.js"] and that's done the trick!

Hey whilst i have you, i used to be able to see a "table" option on my postgres db which would allow me to visually see the data etc.

I believe that's gone because i migrated to a pgvector service template - so i'm guessing that's not supported?

How can i gain access to my pgvector db otherwise? I wasn't aware of the public networking egress charges so i got stung by that, and since then turned it off as I mentioned earlier.

yep that would be why, we only support the viewer on the 1click databases you can create from the canvas (afaik).

You should still be able to access your db using the DATABASE_URL coming out of the pgvector service. you can use it with any database viewer

Hi - i still can't access it via DATABASE_URL.

I definitely have public networking on (see screenshot).

And here's my connection string (with the pw): postgres://postgres:{PASSWORD}@junction.proxy.rlwy.net:57236/railway

I get an error when trying to connect (see second screenshot)

This seems to be an issue specific to your database's setup. Did you change any configurations, and could you try redeploying it?