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
When working with Rails applications, it’s common to use PostgreSQL as the database. While it’s easy to set up a PostgreSQL server on your local machine, it can be a bit cumbersome to manage different versions of PostgreSQL for different projects. Additionally, you might not want to expose the database port so you can be able to run multiple project databases without having to deal with ports.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
posts/using-docker-compose-to-create-project-specific-postgres-for-rails-without-exposing-database-port/
When working with Rails applications, it’s common to use PostgreSQL as the database. While it’s easy to set up a PostgreSQL server on your local machine, it can be a bit cumbersome to manage different versions of PostgreSQL for different projects. Additionally, you might not want to expose the database port so you can be able to run multiple project databases without having to deal with ports.
http://127.0.0.1:4000/posts/using-docker-compose-to-create-project-specific-postgres-for-rails-without-exposing-database-port/
Beta Was this translation helpful? Give feedback.
All reactions