Postgres not showing in every env
A few weeks back I joined Railway for the first time! After that I created multiple environments. I attached a postgres database, and it only went to prod/staging, but not develop.
apparently there was a known bug at the time. To work around this, I created a new postgres database that's just used the develop environment, but for production/staging, I now have a duplicate postgres resource.
What is the fix so i can have a single postgres resource for all my environments? Would I have to delete postgres causing dataloss? π¦
8 Replies
Project ID:
b5aad86a-a209-4a01-bf5c-7ef70197a003b5aad86a-a209-4a01-bf5c-7ef70197a003
Flagging this thread. A team member will be with you shortly.
Hey! So I looked at your project, and there's only one environment (
production) and one Postgres DB. Can you elaborate on what you mean by dupes?I have three environments. PLus the PR environments. My production has 2 postgres services.
my project ID is correct in the chat
Are you sure we're talking the same thing?
Was looking at the wrong project, my bad
I might be missing something but what's stopping you from just deleting one of them that is not in use?
(or re-creating the develop environment)
Is deleteing the develop the only way to get that to work?
Do you not see how that's dangerous for customer working in production? We have a mock data we've create in it
we'd have tear it down and reload it from a backup
lemme see what I can do on my end
no promises and worst case is yeah, you'll have to re-spin the develop environment up π¦
We have no easy way to do this, you'll have to spin the dev environment up again, sorry π
I'll give your team some credits for the inconvenience + cover any potential usages incurred by those duplicates