Warning about Postgres ports being exposed

[plausible]

Warning about Postgres ports being exposed

[ukutaht]

Thanks for reporting the issue. I actually ran into this issue myself over the weekend: https://twitter.com/ukutaht/status/1315280850922156033

How can we fix the Dockerfile so the containers can talk to each other over the local network but the only port exposed to the outside world is 80 or whatever you configure as the webserver's exposed port?

[ukutaht]

Based on quick look online it seems like we should change port mappings to include localhost 127.0.0.1:5432 and define the exposed port on 0.0.0.0:80

[RichGuk]

Yeah, that would work; we could change it to bind to loopback ip instead.

However, plausible_db and plausible_events_db don't actually need the ports exposed. Docker compose will create isolated network for the file, and you're using internal network/hostname in the config. Just remove the ports: section.

If you wanted to access postgres directly you could run:

docker-compose exec plausible_db psql -Upostgres

[ukutaht]

I've removed the port exposure from our default docker-compose.yml file in 891914e

Thanks for reporting!