- Notifications
You must be signed in to change notification settings - Fork1k
fix: restrict database access from outside in docker compose installation#18229
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
github-actionsbot commentedJun 4, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thank you for the contribution@jabacrack
725bc37
intocoder:mainUh oh!
There was an error while loading.Please reload this page.
I think it's better not to expose the database to external access for security reasons.
If external access is absolutely necessary, the user can uncomment the two relevant lines in the Docker Compose file and restart the server.