This repository was archived by the owner on Oct 9, 2025. It is now read-only.
feat: use dedicated storage host for storage lib (allows >50GB uploads) #230
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
grdsdev
approved these changes
Jul 2, 2025
|
🎉 This PR is included in version 2.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 kind of change does this PR introduce?
Feature
What is the current behavior?
Storage lib is initialized using the same host as all other Supabase APIs. This zone does not allow uploading of large files.
What is the new behavior?
Initialize storage lib using new
project-ref.storage.supabase.co/v1URI which supports uploads up to 500GBAdditional context
This is specific to the Supabase infrastructure
project-ref.supabase.co/storage/v1->project-ref.storage.supabase.co/v1