langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #15286] fix: remove port expose on db #28292

New Issue
Closed
opened 2026-02-21 20:43:10 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:43:10 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/15286

State: closed
Merged: Yes

Summary

Closes #15285

In the PR #13836 that introduced the plugin feature, the ports was added to the db in the docker-compose.yml, allowing PostgreSQL to be exposed outside the Docker host by default.

This configuration is unnecessary for typical self-hosting scenarios.

It simply increases the potential for unauthorized access to the database and attacks. Due to the high security risk, the any port should be kept private by default.

Screenshots

Before After
image image

Checklist

Important

Please review the checklist below before submitting your pull request.

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/15286 **State:** closed **Merged:** Yes --- # Summary Closes #15285 In the PR #13836 that introduced the plugin feature, the `ports` was added to the `db` in the `docker-compose.yml`, allowing PostgreSQL to be exposed outside the Docker host by default. This configuration is unnecessary for typical self-hosting scenarios. It simply increases the potential for unauthorized access to the database and attacks. Due to the high security risk, the any port should be kept private by default. # Screenshots | Before | After | |--------|-------| |![image](https://github.com/user-attachments/assets/217b3936-1895-4513-a0bf-cf0e40786b77)| ![image](https://github.com/user-attachments/assets/9e0d117a-2391-46fa-9845-75996483fc03) | # Checklist > [!IMPORTANT] > Please review the checklist below before submitting your pull request. - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [ ] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [ ] I've updated the documentation accordingly. - [ ] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:43:10 -05:00
yindo closed this issue 2026-02-21 20:43:10 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#28292
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?