|
|
|
|
|
by pbronez
789 days ago
|
|
I’m confused about what directions this goes. The announcement is that Supabase now supports (user) —s3 protocol—> (Supabase) Above you say that (Supabase) —Supabase S3 Driver—> (AWS S3) Are you further saying that that (Supabase) —Supabase S3 Driver—> (any S3 compatible storage provider) ? If so, how does the user configure that? It seems more likely that you mean that for any application with the architecture (user) —s3 protocol—> (any S3 compatible storage provider), Supabase can now be swapped in as that storage target. |
|
(user) -> s3 protocol -> (Supabase) -> (AWS S3)
you could fork (or contribute) a database driver for any s3 compatible backend of choice.
(user) -> s3 protocl -> (pbronez-base) -> (GCP Cloud Storage)