docs: document public bucket access and fix custom domain CNAME target#406
Conversation
AI tools were incorrectly telling users that fly.storage.tigris.dev doesn't support anonymous access for public buckets. Add explicit documentation that public buckets are accessible without authentication, with URL examples, to both the Fly SDK guide and the public bucket reference. Assisted-by: Claude Opus 4.6 via Claude Code Co-Authored-By: Claude Opus 4.6 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Greptile SummaryAdds Confidence Score: 5/5Safe to merge — purely documentation additions that accurately reflect product behavior All findings are P2 style only (a single 'the Tigris' phrasing issue); the content is factually correct and fills a real documentation gap docs/sdks/fly/index.md has a minor naming-convention issue on line 87 Important Files Changed
Reviews (1): Last reviewed commit: "docs: clarify public bucket anonymous ac..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| No credentials or signed URLs are needed — the URL works directly in a browser, | ||
| `curl`, `wget`, `<img>` tags, etc. | ||
|
|
||
| Public buckets are also accessible via the Tigris-managed domains |
There was a problem hiding this comment.
Per the project's documentation style rule, the definite article 'the' should not appear directly before 'Tigris'. Rephrase "the Tigris-managed domains" to drop the article.
| Public buckets are also accessible via the Tigris-managed domains | |
| Public buckets are also accessible via Tigris-managed domains |
Rule Used: Don't use the definite article 'the' before 'Tigri... (source)
Learnt From
tigrisdata/tigris-os-docs#262
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| | `BUCKET_NAME.t3.tigrisbucket.io` | `https://foo-public-bucket.t3.tigrisbucket.io/bar.txt` | | ||
| | Domain | Example URL | | ||
| | ------------------------------------ | ---------------------------------------------------------- | | ||
| | `BUCKET_NAME.fly.storage.tigris.dev` | `https://foo-public-bucket.fly.storage.tigris.dev/bar.txt` | |
There was a problem hiding this comment.
Ok so the anonymous access for public access only works on the new .io domains for new users.
The customer in question is an existing customer who are not restricted. So probably this tigris.dev domain doesn't need to be here.
There was a problem hiding this comment.
I believe this comment was on an outdated version?
|
May be we need to clarify that authenticated access to buckets is always done via our t3 or fly.storage endpoint. While serving content via public bucket requires using these new domains |
Update public bucket docs to use t3.tigrisfiles.io as the primary public content domain per the public bucket domains announcement. Remove fly.storage.tigris.dev from the public domains table (it is the S3 API endpoint, not a public content domain). Fix CNAME target for custom domains to t3.tigrisbucket.io. Add custom domain recommendation to the Fly SDK guide. Assisted-by: Claude Opus 4.6 via Claude Code Co-Authored-By: Claude Opus 4.6 <[email protected]>
katieschilling
changed the title
Existing Fly.io accounts can still use fly.storage.tigris.dev for anonymous public access, but this is not available for new accounts. Clarify this in both the Fly SDK guide and public bucket docs to avoid confusing existing users while directing new users to the dedicated public content domains. Assisted-by: Claude Opus 4.6 via Claude Code Co-Authored-By: Claude Opus 4.6 <[email protected]>
Move the fly.storage.tigris.dev existing-account note out of the general public bucket documentation per reviewer feedback. This detail is Fly-specific and already documented in the Fly SDK guide. Assisted-by: Claude Opus 4.6 via Claude Code Co-Authored-By: Claude Opus 4.6 <[email protected]>
…bucket page" This reverts commit dfba3d3.
2 participants
Summary
docs/sdks/fly/index.mdlisting the three dedicated public content domains (t3.tigrisfiles.io,t3.tigrisbucket.io,t3.tigrisblob.io) with examples and a custom domain recommendationdocs/buckets/public-bucket.mdto list the three dedicated public content domainsfly.storage.tigris.devfor public access, but this is not available for new accountst3.storage.devtot3.tigrisbucket.iofly.storage.tigris.devtot3.tigrisbucket.ioContext
A user's AI coding assistant told them that
fly.storage.tigris.dev"does not support anonymous access, even for public buckets." The root cause: the docs only showedfly.storage.tigris.devas the authenticated S3 API endpoint and didn't clearly document the dedicated public content domains or that public bucket objects are anonymously accessible.Per the public bucket domains announcement, new accounts serve public content from
t3.tigrisfiles.io(and two alternate domains), separate from the API infrastructure. Existing accounts can continue usingfly.storage.tigris.devfor public access. Custom domain CNAMEs should point toBUCKET.t3.tigrisbucket.io.Companion PR to Fly docs: superfly/docs#2372
Test plan
npm run buildpassesnpm run lintpasses (prettier clean on changed files)🤖 Generated with Claude Code
Note
Low Risk
Low risk documentation-only changes; main risk is potential confusion if domain guidance is incorrect or incomplete.
Overview
Public bucket access docs are updated to explicitly document anonymous reads via the dedicated public content domains (
t3.tigrisfiles.io,t3.tigrisbucket.io,t3.tigrisblob.io), including examples and guidance that the domains are interchangeable.Adds notes that
*.fly.storage.tigris.devpublic access remains for existing Fly.io accounts only, and fixes custom domain CNAME instructions to point toBUCKET_NAME.t3.tigrisbucket.io(including in the Fly SDK docs), with a recommendation to use custom domains for production.Reviewed by Cursor Bugbot for commit 1e87ca2. Bugbot is set up for automated code reviews on this repo. Configure here.