langgenius/dify-docs-archived
1
0
Fork 0
mirror of https://github.com/langgenius/dify-docs-archived.git synced 2026-07-19 14:33:40 -04:00
Code Issues 39 Packages Projects Releases Wiki Activity

Enterprise Solutions Deployment #88

New Issue
Open
opened 2026-02-16 11:19:43 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 11:19:43 -05:00
Owner
Copy Link
Copy Source

Originally created by @benjamin-mogensen on GitHub (Mar 4, 2025).

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.

To support a structured and efficient deployment process, we require enhanced deployment capabilities within Dify:

  • Automated Environment Deployment: The ability to deploy applications from development to production without manual import/export of DSL files.
  • Scheduled Deployments: Deployments should be schedulable to allow for controlled rollouts.
  • Rollback Capability: A mechanism to revert to a previous deployment state in case of failures.
  • Error Handling: Built-in error detection and handling to prevent failed or partial deployments.
  • Data Tier & Knowledge Base Deployment: Deployment and rollback should extend to the data tier, including any knowledge bases or embedded data sources.

2. Additional context or comments

@crazywoola @guchenhe

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @benjamin-mogensen on GitHub (Mar 4, 2025). ### 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. To support a structured and efficient deployment process, we require enhanced deployment capabilities within Dify: - Automated Environment Deployment: The ability to deploy applications from development to production without manual import/export of DSL files. - Scheduled Deployments: Deployments should be schedulable to allow for controlled rollouts. - Rollback Capability: A mechanism to revert to a previous deployment state in case of failures. - Error Handling: Built-in error detection and handling to prevent failed or partial deployments. - Data Tier & Knowledge Base Deployment: Deployment and rollback should extend to the data tier, including any knowledge bases or embedded data sources. ### 2. Additional context or comments @crazywoola @guchenhe ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the enhancement label 2026-02-16 11:19:43 -05:00
yindo commented 2026-02-16 11:19:43 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 4, 2025):

Regarding this feature request, Enterprise solution is supported via our enterprise version. Please contact our business team to get a quota via business@dify.ai.

Besides that, we do not provide this feature for community version.

@crazywoola commented on GitHub (Mar 4, 2025): Regarding this feature request, Enterprise solution is supported via our enterprise version. Please contact our business team to get a quota via business@dify.ai. Besides that, we do not provide this feature for community version.
yindo commented 2026-02-16 11:19:44 -05:00
Author
Owner
Copy Link
Copy Source

@benjamin-mogensen commented on GitHub (Mar 4, 2025):

Regarding this feature request, Enterprise solution is supported via our enterprise version. Please contact our business team to get a quota via business@dify.ai.

Besides that, we do not provide this feature for community version.

@crazywoola I agreed with @guchenhe that the process is to create the feature requests as issues here. So I am bit puzzled by you closing the issue. Where do I then, as an enterprise customer, track the process of, and the agreed details of requirement and solution, of the individual feature requests?

@benjamin-mogensen commented on GitHub (Mar 4, 2025): > Regarding this feature request, Enterprise solution is supported via our enterprise version. Please contact our business team to get a quota via business@dify.ai. > > Besides that, we do not provide this feature for community version. @crazywoola I agreed with @guchenhe that the process is to create the feature requests as issues here. So I am bit puzzled by you closing the issue. Where do I then, as an enterprise customer, track the process of, and the agreed details of requirement and solution, of the individual feature requests?
yindo commented 2026-02-16 11:19:44 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 5, 2025):

@benjamin-mogensen I see, I just got the messages from her. I will reopen this issue, you can use this milestone to track all enterprise related issue https://github.com/langgenius/dify/milestone/14

@crazywoola commented on GitHub (Mar 5, 2025): @benjamin-mogensen I see, I just got the messages from her. I will reopen this issue, you can use this milestone to track all enterprise related issue https://github.com/langgenius/dify/milestone/14
yindo commented 2026-02-16 11:19:44 -05:00
Author
Owner
Copy Link
Copy Source

@benjamin-mogensen commented on GitHub (Apr 22, 2025):

@Yawen-1010 this is still to be open as it is not implemented/ released yet.

@benjamin-mogensen commented on GitHub (Apr 22, 2025): @Yawen-1010 this is still to be open as it is not implemented/ released yet.
yindo commented 2026-02-16 11:19:44 -05:00
Author
Owner
Copy Link
Copy Source

@Yawen-1010 commented on GitHub (Apr 23, 2025):

Hi, @benjamin-mogensen. Sure, no problem. I saw my colleague reopened this issue on Mar 5. We can keep it open and follow up on the progress of this feature.

Image
@Yawen-1010 commented on GitHub (Apr 23, 2025): Hi, @benjamin-mogensen. Sure, no problem. I saw my colleague reopened this issue on Mar 5. We can keep it open and follow up on the progress of this feature. <img width="337" alt="Image" src="https://github.com/user-attachments/assets/e700e07a-aa12-4f33-bacb-971e25cc1b70" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
documentation
enhancement
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-docs-archived#88
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?