You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Service A needs to have three urls when accessing self-built Dify.
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.
The text was updated successfully, but these errors were encountered:
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.
Self Checks
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.
Service A needs to have three urls when accessing self-built Dify.
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?
The text was updated successfully, but these errors were encountered: