Provision Dify on Cloud automatically?
nikawang opened this issue · comments
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.
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.
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.