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

multiple environment needed #11917

Closed
5 tasks done
mboo2005 opened this issue Dec 20, 2024 · 1 comment
Closed
5 tasks done

multiple environment needed #11917

mboo2005 opened this issue Dec 20, 2024 · 1 comment
Labels
💪 enhancement New feature or request

Comments

@mboo2005
Copy link

mboo2005 commented Dec 20, 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.

How does Dify support different development environments? For example, there are three sets of environments: development, testing, and release.
System architecture: service A—>self-hosted dify—>tool api
Each service needs three environments such as dev test and prod.

  1. Service A needs to have three urls when accessing self-built Dify.

  2. When Dify accesses downstream tools, it also needs to select tools in different environments according to the environment.
    Example: a-dev.foo.com requests dev.Dify, and dev.Dify requests dev.tool.com.

How can this be achieved? Currently, I can only deploy three different Dify environments to achieve this, which is too troublesome. Workflows and tools all need to be configured three times. Is there a better mechanism?

2. Additional context or comments

No

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 Dec 20, 2024
@crazywoola
Copy link
Member

How can this be achieved? Currently, I can only deploy three different Dify environments to achieve this, which is too troublesome. Workflows and tools all need to be configured three times. Is there a better mechanism?

No, we do the same as well. For example, we have dev env and stg env and prod env which is cloud.dify.ai. The only difference is the env settings, besides there is no difference.

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

No branches or pull requests

2 participants