Update docs to specify HTTP for SeaweedFS#9149
Open
AGSPhoenix wants to merge 3 commits intorclone:masterfrom
Open
Update docs to specify HTTP for SeaweedFS#9149AGSPhoenix wants to merge 3 commits intorclone:masterfrom
AGSPhoenix wants to merge 3 commits intorclone:masterfrom
Conversation
Should help reduce issues like rclone#8572
ncw
requested changes
Feb 17, 2026
Member
ncw
left a comment
There was a problem hiding this comment.
Sorry for the delay in replying.
This fix needs to go in https://github.com/rclone/rclone/blob/master/backend/s3/provider/SeaweedFS.yaml
as the docs are autogenerated from there.
Thanks
Member
|
@AGSPhoenix do you want to update the doc fix to the correct file?
|
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
2 participants
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.
What is the purpose of this change?
The SeaweedFS endpoint currently recommended by the docs will cause rclone to hang with no apparent cause. This change explicitly shows the use of HTTP to match the standard SeaweedFS deplopyment.
Was the change discussed in an issue or in the forum before?
#8572
Checklist
Solidly into yak shaving territory putting in this PR; gonna go figure out the SeaweedFS issue I started on 30 minutes ago and fix the commit title later. In the meantime, discussion on whether we want to encourage use of HTTP for an entirely local S3 provider is welcome.