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

[PR #126] [MERGED] Docs: update Deploy with Docker Compose. #390

New Issue
Closed
opened 2026-02-16 06:15:21 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 06:15:21 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-docs/pull/126
Author: @fernvenue
Created: 5/21/2025
Status: ✅ Merged
Merged: 7/8/2025
Merged by: @guchenhe

Base: main ← Head: main

📝 Commits (5)

  • e9ec471 Add backup before upgrading.
  • a745873 Dynamically retrieve the latest version in the installation steps using jq.
  • 16be8fb Add ZIP archive way for installation and upgrading.
  • 5484b22 Move some parts to FAQ page.
  • e0b95a7 Merge branch 'main' into main

📊 Changes

2 files changed (+44 additions, -7 deletions)

View changed files

📝 en/getting-started/install-self-hosted/docker-compose.mdx (+1 -2)
📝 en/getting-started/install-self-hosted/faqs.mdx (+43 -5)

📄 Description

This PR includes several updates:

  • Add backup before upgrading;

I think it's really important that backup the current user data, we can't sure we will never have any breaking change right? So I think this is a good idea maybe?

  • Dynamically retrieve the latest version in the installation steps;

Here the user needs to check the latest version, which might be a bit cumbersome. And some users may think that the version in the documentation is the latest version, thus installing an old version. I think it would be better to use jq to fetch the latest version number from the GitHub API in the command.

  • Add ZIP archive way for installation and upgrading.

I think this will be very useful for some restricted networks?

Anyway, feel free to point out any issues :)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-docs/pull/126 **Author:** [@fernvenue](https://github.com/fernvenue) **Created:** 5/21/2025 **Status:** ✅ Merged **Merged:** 7/8/2025 **Merged by:** [@guchenhe](https://github.com/guchenhe) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (5) - [`e9ec471`](https://github.com/langgenius/dify-docs/commit/e9ec4711336fe20edfb85b642d9bb0f8dd94b985) Add backup before upgrading. - [`a745873`](https://github.com/langgenius/dify-docs/commit/a7458735e299c64c21611ac1ecb2e3c7d2238e78) Dynamically retrieve the latest version in the installation steps using jq. - [`16be8fb`](https://github.com/langgenius/dify-docs/commit/16be8fb15362f0191504e2579b6024e3b8c1073c) Add ZIP archive way for installation and upgrading. - [`5484b22`](https://github.com/langgenius/dify-docs/commit/5484b22eeacab3150559343e59370ff7beae9c93) Move some parts to FAQ page. - [`e0b95a7`](https://github.com/langgenius/dify-docs/commit/e0b95a7d8c92d93114f7c9fad96bc7902049f8d4) Merge branch 'main' into main ### 📊 Changes **2 files changed** (+44 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `en/getting-started/install-self-hosted/docker-compose.mdx` (+1 -2) 📝 `en/getting-started/install-self-hosted/faqs.mdx` (+43 -5) </details> ### 📄 Description This PR includes several updates: - Add backup before upgrading; I think it's really important that backup the current user data, we can't sure we will never have any breaking change right? So I think this is a good idea maybe? - Dynamically retrieve the latest version in the installation steps; Here the user needs to check the latest version, which might be a bit cumbersome. And some users may think that the version in the documentation is the latest version, thus installing an old version. I think it would be better to use `jq` to fetch the latest version number from the GitHub API in the command. - Add ZIP archive way for installation and upgrading. I think this will be very useful for some restricted networks? Anyway, feel free to point out any issues :) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 06:15:21 -05:00
yindo closed this issue 2026-02-16 06:15:21 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
documentation
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label pull-request
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#390
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?