Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update docker-compose.yml stop exposing ports publicly #4270

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

fhackenberger
Copy link

You don't want ports exposed publicly, bypassing many firewall set-ups, just by trying out this docker-compose.yml. Better only bind them to 127.0.0.1

You don't want ports exposed publicly, bypassing many firewall set-ups, just by trying out this docker-compose.yml. Better only bind them to 127.0.0.1
@fhackenberger fhackenberger requested a review from a team as a code owner April 23, 2024 16:24
@CLAassistant
Copy link

CLAassistant commented Apr 23, 2024

CLA assistant check
All committers have signed the CLA.

@matiasb
Copy link
Collaborator

matiasb commented Apr 24, 2024

Thanks for the contribution. This docker-compose file is mainly for hobby setups/testing, and in some cases it is still useful to have the ports accessible in the network. Maybe we could update the readme or docs to mention this instead?

@fhackenberger
Copy link
Author

Imho especially Hobbyist should have a security by default set-up as they might be less aware of the consequences. It would be easy to add a commented out BIND_TO=0.0.0.0 into the .env, so they can easily re-enable it if they need the service on the network. Would you accept the PR, if I add this?

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.

None yet

4 participants