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

Docker deployment self-hosted versus cloud #1018

New Issue
Closed
opened 2026-02-21 17:29:31 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 17:29:31 -05:00
Owner
Copy Link
Copy Source

Originally created by @ghost on GitHub (Feb 1, 2024).

Self Checks

Provide a description of the help you need

I know it's in the documentation you can set cloud or self-hosted when you launch for docker. If we're able to set it for cloud which means we have to use GitHub or Google login, what are the URLs we have to authorize for that? For JavaScript and call back?

Originally created by @ghost on GitHub (Feb 1, 2024). ### 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 file this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). ### Provide a description of the help you need I know it's in the documentation you can set cloud or self-hosted when you launch for docker. If we're able to set it for cloud which means we have to use GitHub or Google login, what are the URLs we have to authorize for that? For JavaScript and call back?
yindo added the 📚 documentation label 2026-02-21 17:29:31 -05:00
yindo closed this issue 2026-02-21 17:29:31 -05:00
yindo commented 2026-02-21 17:29:31 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 1, 2024):

🤖

Hey @vontainment! Great to see you back here with another insightful question. 🚀

For GitHub login when setting up a cloud-based Docker deployment for the dify repository, you would need to authorize the following URLs:

  1. Access Tokens URL: https://github.com/settings/tokens?type=beta
  2. API Version URL: https://docs.github.com/en/rest/about-the-rest-api/api-versions?apiVersion=2022-11-28

These URLs are specified in the github.yaml file under the credentials_for_provider section. The access_tokens field requires the URL for generating GitHub access tokens, and the api_version field requires the URL for the GitHub API version documentation. You can find this file in the repository at api/core/tools/provider/builtin/github/github.yaml.

As for the Google login URLs, I'm afraid I don't have that information based on the provided context. You might need to refer to the Google Cloud documentation or the specific file in the dify repository that handles Google login for that information.

Regarding the process of setting up a cloud-based Docker deployment for the dify repository, here are the general steps:

  1. Build the Docker Image: Use the Dockerfile provided in the repository to build a Docker image. The command for this is docker build -t dify:latest ..

  2. Push the Docker Image to a Registry: After building the Docker image, push it to a Docker registry. If you're using Docker Hub, you can use the following commands, replacing username with your Docker Hub username:

docker tag dify:latest username/dify:latest
docker push username/dify:latest
  1. Deploy the Docker Image: Deploy the Docker image to a cloud provider that supports Docker containers. The specific steps for this will depend on your cloud provider.

Remember to replace the CONSOLE_API_URL and APP_API_URL environment variables in the Dockerfile with the actual URLs of your services. Also, ensure that the cloud provider's security settings allow traffic on port 3000, as specified in the Dockerfile. You can find the Dockerfile in the repository at web/Dockerfile.

Please let me know if you need further clarification or assistance.

Sources

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot[bot] commented on GitHub (Feb 1, 2024): _🤖_ <!-- Greeting --> Hey @vontainment! Great to see you back here with another insightful question. 🚀 <!-- Answer --> For GitHub login when setting up a cloud-based Docker deployment for the dify repository, you would need to authorize the following URLs: 1. Access Tokens URL: `https://github.com/settings/tokens?type=beta` 2. API Version URL: `https://docs.github.com/en/rest/about-the-rest-api/api-versions?apiVersion=2022-11-28` These URLs are specified in the `github.yaml` file under the `credentials_for_provider` section. The `access_tokens` field requires the URL for generating GitHub access tokens, and the `api_version` field requires the URL for the GitHub API version documentation. You can find this file in the repository at [api/core/tools/provider/builtin/github/github.yaml](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/github/github.yaml). As for the Google login URLs, I'm afraid I don't have that information based on the provided context. You might need to refer to the Google Cloud documentation or the specific file in the dify repository that handles Google login for that information. Regarding the process of setting up a cloud-based Docker deployment for the dify repository, here are the general steps: 1. **Build the Docker Image**: Use the Dockerfile provided in the repository to build a Docker image. The command for this is `docker build -t dify:latest .`. 2. **Push the Docker Image to a Registry**: After building the Docker image, push it to a Docker registry. If you're using Docker Hub, you can use the following commands, replacing `username` with your Docker Hub username: ```bash docker tag dify:latest username/dify:latest docker push username/dify:latest ``` 3. **Deploy the Docker Image**: Deploy the Docker image to a cloud provider that supports Docker containers. The specific steps for this will depend on your cloud provider. Remember to replace the `CONSOLE_API_URL` and `APP_API_URL` environment variables in the Dockerfile with the actual URLs of your services. Also, ensure that the cloud provider's security settings allow traffic on port 3000, as specified in the Dockerfile. You can find the Dockerfile in the repository at [web/Dockerfile](https://github.com/langgenius/dify/blob/main/web/Dockerfile). Please let me know if you need further clarification or assistance. ## Sources - [api/core/tools/provider/builtin/github/github.yaml](https://github.com/langgenius/dify/blob/main/api/core/tools/provider/builtin/github/github.yaml) - [web/Dockerfile](https://github.com/langgenius/dify/blob/main/web/Dockerfile) --- This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot.
yindo commented 2026-02-21 17:29:31 -05:00
Author
Owner
Copy Link
Copy Source

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

For cloud version deployment, please contact business@dify.ai, it requires our business license to get technical support of that.

@crazywoola commented on GitHub (Feb 1, 2024): For cloud version deployment, please contact business@dify.ai, it requires our business license to get technical support of that.
yindo commented 2026-02-21 17:29:31 -05:00
Author
Owner
Copy Link
Copy Source

@ghost commented on GitHub (Feb 2, 2024):

Ah. You should probably put a note in the documents for that.

@ghost commented on GitHub (Feb 2, 2024): Ah. You should probably put a note in the documents for that.
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 📚 documentation
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#1018
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?