Skip to content

Fix #8 by removing postgres port map#16

Open
mrmanc wants to merge 1 commit into
masterfrom
remove-port-clash
Open

Fix #8 by removing postgres port map#16
mrmanc wants to merge 1 commit into
masterfrom
remove-port-clash

Conversation

@mrmanc

@mrmanc mrmanc commented May 9, 2022

Copy link
Copy Markdown
Member

We don’t need to expose the postgres port on the host. The containers communicate via their own ports on the bridge network. Exposing the postgres port on 5432 can lead to port clashes with existing postgres instances. If we want to expose postgres, we should do it on something like port 54321, but we don’t need to change the connect strings etc elsewhere as they still communicate via 5432 on the bridge network.

It would be good for someone else to verify that this still works before merging.

We don’t need to expose the postgres port on the host. The containers communicate via their own ports on the bridge network. Exposing the postgres port on `5432` can lead to port clashes with existing postgres instances. If we want to expose postgres, we should do it on something like port `54321`, *but* we don’t need to change the connect strings etc elsewhere as they still communicate via `5432` on the bridge network.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant