You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should the name of the postgres service linked to my application at Dokku match the database name in database.yml, so that I am expected to create the service with the following command:
dokku postgres:create derp_app_production
Or is it possible to use a different name without raising conflicts?
dokku postgres:create derp
The text was updated successfully, but these errors were encountered:
@josegonzalez I understood how to assign a name to a postgres service, thank you.
However, I was mainly concerned about what name to choose and if there is any restriction.
In Ruby on Rails, the database configuration file is config/database.yml where each environment has its own configuration records, included the database name which is inferred by the name of the application: application_name_environment.
So, for the production environment we have application_name_production. There are also other useful records, such as the connection pool.
So I wonder: do I have to stick with the name contained in config/database.yml when I assign a name to the postgres service?
We don't currently allow you to rename the postgres database that is created when you create a postgres service, so your best bet is to name it application_name_environment and then link appropriately.
IIRC you can just change the name in your config/database.yml to match the loaded service.
The
database.yml
file of my Ruby on Rails application contains the following record:Should the name of the postgres service linked to my application at Dokku match the database name in
database.yml
, so that I am expected to create the service with the following command:Or is it possible to use a different name without raising conflicts?
The text was updated successfully, but these errors were encountered: