langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-27 11:11:21 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

.env configuration pull from "configuration center" #6924

New Issue
Closed
opened 2026-02-21 18:17:58 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:17:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @huanshare on GitHub (Nov 25, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

  Now the dify project API configuration is written in the .env file,but in the enterprise, the middleware-related passwords are strictly confidential. 
 Can we put the .env configuration in the "configuration center" instead of writing it in the project .env file? When the project starts, we can first pull the configuration, write it to the .env file, and then load subsequent operations.
 Just like using 'apollo' or 'nacos' to manage project configuration.

2. Additional context or comments

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @huanshare on GitHub (Nov 25, 2024). ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Now the dify project API configuration is written in the .env file,but in the enterprise, the middleware-related passwords are strictly confidential. Can we put the .env configuration in the "configuration center" instead of writing it in the project .env file? When the project starts, we can first pull the configuration, write it to the .env file, and then load subsequent operations. Just like using 'apollo' or 'nacos' to manage project configuration. ### 2. Additional context or comments ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:17:58 -05:00
yindo closed this issue 2026-02-21 18:17:58 -05:00
yindo commented 2026-02-21 18:17:59 -05:00
Author
Owner
Copy Link
Copy Source

@shiyiyue1102 commented on GitHub (Mar 24, 2025):

Can DIFY integrate Nacos as an external configuration center？

@shiyiyue1102 commented on GitHub (Mar 24, 2025): Can DIFY integrate Nacos as an external configuration center？
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 💪 enhancement
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#6924
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?