docs: note that s3fs template works with any S3-compatible provider#195
Open
davidmyriel wants to merge 1 commit intoe2b-dev:mainfrom
Open
docs: note that s3fs template works with any S3-compatible provider#195davidmyriel wants to merge 1 commit intoe2b-dev:mainfrom
davidmyriel wants to merge 1 commit intoe2b-dev:mainfrom
Conversation
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
Adds a short "Other S3-compatible providers" section at the end of
docs/sandbox/connect-bucket.mdxnoting that the existings3fssetup generalizes to any S3-compatible object storage provider via the-o url=flag already demonstrated in the Cloudflare R2 example.Names Tigris, MinIO, and Backblaze B2 as examples so readers searching for those specifically can find confirmation that the existing template works for them, without adding a dedicated section per provider.
Why
The doc currently has per-provider sections for GCS, Amazon S3, and Cloudflare R2. The R2 section already implicitly teaches the generic pattern (override endpoint with
-o url=), but a reader looking for any other provider has to infer that it applies to them. A four-line note makes that explicit and avoids future per-provider section sprawl.Changes
docs/sandbox/connect-bucket.mdx: new short section at the end, no new code blocks, points back to the existing R2 example