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
Using one server for the application and a different one for the database seems to be a common pattern.
We define a database_hostname which is used in the generated database.yml file. It would be great if the tasks creating the database, its users and its extensions were executed on the server defined in database_hostname.
Alternatively, we could provide some kind of condition to easily skip these steps so they don't run when we're using a separate database server.
The text was updated successfully, but these errors were encountered:
javierm
changed the title
Allow using a different server for the database
Allow using a separate database server
Mar 30, 2023
Using one server for the application and a different one for the database seems to be a common pattern.
We define a
database_hostname
which is used in the generateddatabase.yml
file. It would be great if the tasks creating the database, its users and its extensions were executed on the server defined indatabase_hostname
.Alternatively, we could provide some kind of condition to easily skip these steps so they don't run when we're using a separate database server.
The text was updated successfully, but these errors were encountered: