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

.env configuration pull from "configuration center" #11064

Open
5 tasks done
huanshare opened this issue Nov 25, 2024 · 0 comments · May be fixed by #11139
Open
5 tasks done

.env configuration pull from "configuration center" #11064

huanshare opened this issue Nov 25, 2024 · 0 comments · May be fixed by #11139
Assignees
Labels
💪 enhancement New feature or request

Comments

@huanshare
Copy link

huanshare commented 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.
@dosubot dosubot bot added the 💪 enhancement New feature or request label Nov 25, 2024
huanshare pushed a commit to huanshare/dify that referenced this issue Nov 26, 2024
@huanshare huanshare linked a pull request Nov 26, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💪 enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant