Docs: add S3 persistent storage configuration#36
Merged
Winson-030 merged 1 commit intoWinson-030:upgrade/dify-version-100from Apr 17, 2025
Merged
Conversation
Owner
|
Thanks for your great contribution Aki san. I will review ASAP. |
Winson-030
approved these changes
Apr 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✨ Summary
I am planning to add documentation on setting up the use of the cloud as persistent storage for Dify, which seems to be in demand.
I will add multilingual documentation using AWS S3 as an example.
This document explains how to switch from local storage (
/app/api/storage) to AWS S3 using environment variables in the Kubernetes manifest.It is written in Japanese, English, and Chinese to support a wider range of users and contributors.
Changes
api.yamlandworker.yaml.💬 Notes.
We would like to add documentation on storage configuration.
I have created a README under
dify/api/as a section close to the code, but it would be helpful if you could review if this policy is acceptable!