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

[PR #18279] Uniformly name the dify containers #28876

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

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

State: closed
Merged: No

Summary

fixes #18274

In scenarios where many containers are working simultaneously, the default container naming of dif is confusing. Therefore, in this commit, all containers have been uniformly named and the prefix "dify_" has been uniformly used to facilitate their use in multi-container scenarios.

Screenshots

$ docker ps
CONTAINER ID   NAMES                STATUS                            PORTS
695e3e2e7cfd   dify_nginx           Up 59 minutes                     0.0.0.0:11180->80/tcp, :::11180->80/tcp, 0.0.0.0:11443->443/tcp, :::11443->443/tcp
d07a877ba323   dify_worker          Up 59 minutes                     5001/tcp
6e4a932bb78a   dify_api             Up 59 minutes                     5001/tcp
b7f7a3eb3ed3   dify_plugin_daemon   Up 59 minutes                     0.0.0.0:5003->5003/tcp, :::5003->5003/tcp
f1592ed91c63   dify_sandbox         Up 59 minutes (healthy)
4ae0fb2412cd   dify_db              Up 59 minutes (healthy)           5432/tcp
b14803ca890e   dify_web             Up 59 minutes                     3000/tcp
8aa536ebc778   dify_ssrf_proxy      Up 59 minutes                     3128/tcp
5fc84eaee476   dify_weaviate        Up 59 minutes
c50cad34b0eb   dify_redis           Up 59 minutes (healthy)           6379/tcp

Checklist

Important

Please review the checklist below before submitting your pull request.

  • This change requires a documentation update, included: Dify Document （No document changes are involved）
  • 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.（Just modify the name and there is no need for testing）
  • I've updated the documentation accordingly.（It does not involve the content of the document）
  • 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/18279 **State:** closed **Merged:** No --- # Summary fixes #18274 In scenarios where many containers are working simultaneously, the default container naming of dif is confusing. Therefore, in this commit, all containers have been uniformly named and the prefix "dify_" has been uniformly used to facilitate their use in multi-container scenarios. # Screenshots ``` $ docker ps CONTAINER ID NAMES STATUS PORTS 695e3e2e7cfd dify_nginx Up 59 minutes 0.0.0.0:11180->80/tcp, :::11180->80/tcp, 0.0.0.0:11443->443/tcp, :::11443->443/tcp d07a877ba323 dify_worker Up 59 minutes 5001/tcp 6e4a932bb78a dify_api Up 59 minutes 5001/tcp b7f7a3eb3ed3 dify_plugin_daemon Up 59 minutes 0.0.0.0:5003->5003/tcp, :::5003->5003/tcp f1592ed91c63 dify_sandbox Up 59 minutes (healthy) 4ae0fb2412cd dify_db Up 59 minutes (healthy) 5432/tcp b14803ca890e dify_web Up 59 minutes 3000/tcp 8aa536ebc778 dify_ssrf_proxy Up 59 minutes 3128/tcp 5fc84eaee476 dify_weaviate Up 59 minutes c50cad34b0eb dify_redis Up 59 minutes (healthy) 6379/tcp ``` # 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) （No document changes are involved） - [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.（Just modify the name and there is no need for testing） - [ ] I've updated the documentation accordingly.（It does not involve the content of the document） - [x] 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:44:17 -05:00
yindo closed this issue 2026-02-21 20:44:17 -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#28876
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?