4 days ago
I made a copy of my environment (staging copied to production)
both environment have their own postgres database, yet when I rename the postgres service on staging is automatically updates the name on production.
This seems unusual behaviour no ?
The agent says that: service names are global across your entire project.
not sure this is correct if the services are distinct.
Ideally I want my my staging postgres service to be calles postgres-staging and my production one to be called postgres-production.
Any help welcomed.
Thanks
2 Replies
4 days ago
That's correct, service names are project-wide, not per-environment. Renaming a service in one environment renames it everywhere. To give each database a distinct name, you would need separate services rather than the same service across environments. That said, when you clone an environment, each environment already gets its own independent Postgres instance (with its own volume and credentials), so the underlying databases are fully isolated even though they share a service name.
Status changed to Awaiting User Response Railway • 4 days ago
Railway
That's correct, service names are project-wide, not per-environment. Renaming a service in one environment renames it everywhere. To give each database a distinct name, you would need separate services rather than the same service across environments. That said, when you clone an environment, each environment already gets its own independent Postgres instance (with its own volume and credentials), so the underlying databases are fully isolated even though they share a service name.
4 days ago
thanks for clarifying that!
Status changed to Awaiting Railway Response Railway • 4 days ago
Status changed to Solved Railway • 4 days ago