langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Provision Dify on Cloud automatically? #4351

New Issue
Closed
opened 2026-02-21 18:06:01 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:06:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @nikawang on GitHub (Jun 30, 2024).

Originally assigned to: @crazywoola on GitHub.

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).
  • 请务必使用英文提交 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.

Currently, the official dify only supports one-click rapid deployment using docker-compose. However, if we wish to have a self-hosted dify service that is more stable and reliable on cloud platforms, services like PostgreSQL and Redis can utilize PaaS offerings from cloud services, while other dify-related application components can be run on the cloud platform's container services. Leveraging the capabilities of cloud platforms allows for on-demand usage, improving resource utilization, reducing costs, and ensuring the stability and high availability of the platform.

2. Additional context or comments

I have now completed the integration with Azure using Terraform. Here's the setup:

Front-end access:

  • nginx -> Azure Container Apps (Serverless)

Back-end components:

  • web -> Azure Container Apps (Serverless)
  • api -> Azure Container Apps (Serverless)
  • worker -> Azure Container Apps (minimum of 1 instance)
  • sandbox -> Azure Container Apps (Serverless)
  • ssrf_proxy -> Azure Container Apps (Serverless)
  • db -> Azure Database for PostgreSQL
  • vectordb -> Azure Database for PostgreSQL
  • redis -> Azure Cache for Redis

Should we consider merging this code into the dify community repository? Please check dify-azure-tf-files

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @nikawang on GitHub (Jun 30, 2024). Originally assigned to: @crazywoola on GitHub. ### 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] 请务必使用英文提交 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. Currently, the official dify only supports one-click rapid deployment using docker-compose. However, if we wish to have a self-hosted dify service that is more stable and reliable on cloud platforms, services like PostgreSQL and Redis can utilize PaaS offerings from cloud services, while other dify-related application components can be run on the cloud platform's container services. Leveraging the capabilities of cloud platforms allows for on-demand usage, improving resource utilization, reducing costs, and ensuring the stability and high availability of the platform. ### 2. Additional context or comments I have now completed the integration with Azure using Terraform. Here's the setup: Front-end access: - nginx -> Azure Container Apps (Serverless) Back-end components: - web -> Azure Container Apps (Serverless) - api -> Azure Container Apps (Serverless) - worker -> Azure Container Apps (minimum of 1 instance) - sandbox -> Azure Container Apps (Serverless) - ssrf_proxy -> Azure Container Apps (Serverless) - db -> Azure Database for PostgreSQL - vectordb -> Azure Database for PostgreSQL - redis -> Azure Cache for Redis Should we consider merging this code into the dify community repository? Please check [dify-azure-tf-files](https://github.com/nikawang/dify/tree/main/azure/tf/aca) ### 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:06:01 -05:00
yindo closed this issue 2026-02-21 18:06:02 -05:00
yindo commented 2026-02-21 18:06:02 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 1, 2024):

Hello there, thanks for interesting in contributing to this feature. You can add my WeChat crazyphage if you are willing to talk to our dev team.

@crazywoola commented on GitHub (Jul 1, 2024): Hello there, thanks for interesting in contributing to this feature. You can add my WeChat crazyphage if you are willing to talk to our dev team.
yindo commented 2026-02-21 18:06:02 -05:00
Author
Owner
Copy Link
Copy Source

@saendu commented on GitHub (Jul 12, 2024):

I've tested it and it worked. The certificate aca-cert-path and aca-cert-password is no more needed I think (deprecated). However I cannot make the 'HTTP Request' step in a workflow work. I always get a timeout. It could be a connectivity issue or a bug. Not yet sure. I will open a new issue.

@saendu commented on GitHub (Jul 12, 2024): I've tested it and it worked. The certificate aca-cert-path and aca-cert-password is no more needed I think (deprecated). However I cannot make the 'HTTP Request' step in a workflow work. I always get a timeout. It could be a connectivity issue or a bug. Not yet sure. I will open a new issue.
yindo commented 2026-02-21 18:06:02 -05:00
Author
Owner
Copy Link
Copy Source

@saendu commented on GitHub (Aug 29, 2024):

I am trying to reduce my costs regarding this terraform script. @nikawang maybe you have already found out what the minimal requirements are? I've opened a discussion here: https://github.com/langgenius/dify/discussions/7814

@saendu commented on GitHub (Aug 29, 2024): I am trying to reduce my costs regarding this terraform script. @nikawang maybe you have already found out what the minimal requirements are? I've opened a discussion here: https://github.com/langgenius/dify/discussions/7814
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#4351
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?