mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 01:45:10 +03:00
Moved Youtube Video
Moved Youtube video to the Deep Dive Resume Uploads.
This commit is contained in:
1 parent
0db31c1dde
commit
fc7286db01
1 file changed
+11
-11
@@ -13,17 +13,6 @@ thumb: launch-week-7/day-3-storage-resumable-uploads/storage-v3-thumb.jpg
|
||||
|
||||
Supabase Storage is receiving a major upgrade, implementing many of the most requested features from our users: Resumable Uploads , Quality Filters, Next.js support, and WebP support.
|
||||
|
||||
<div className="video-container">
|
||||
<iframe
|
||||
className="w-full"
|
||||
src="https://www.youtube-nocookie.com/embed/pT2PcZFq_M0"
|
||||
title="YouTube video player"
|
||||
frameborder="0"
|
||||
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
|
||||
allowfullscreen
|
||||
></iframe>
|
||||
</div>
|
||||
|
||||
The key feature: **Resumable Uploads**! With Resumable Uploads, you can continue uploading a file from where you left off, even if you lose internet connectivity or accidentally close your browser tab while uploading.
|
||||
|
||||
Resumable uploads divides the file into chucks before uploading them, emitting progress events during upload.
|
||||
@@ -113,6 +102,17 @@ For example, you can restrict your users a 1 MB and `image/*` files when uploadi
|
||||
|
||||
## Deep Dive into Resumable Uploads
|
||||
|
||||
<div className="video-container">
|
||||
<iframe
|
||||
className="w-full"
|
||||
src="https://www.youtube-nocookie.com/embed/pT2PcZFq_M0"
|
||||
title="YouTube video player"
|
||||
frameborder="0"
|
||||
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
|
||||
allowfullscreen
|
||||
></iframe>
|
||||
</div>
|
||||
|
||||
Let’s get into the nuts-and-bolts of how we implemented Resumable Uploads.
|
||||
|
||||
First, why do we need Resumable Uploads, when the HTTP protocol has a standard method for uploading files - **`multipart/form-data`** ? This approach works well for small files, since the file is streamed to the server in bytes over the network. For medium to large files this method becomes problematic, especially on spotty connections like mobile networks. Uploads that are interrupted need to be restarted from the beginning.
|
||||
|
||||
Reference in new issue
Block a user