Live data from Hacker News

Supabase Storage now supports the S3 protocol

supabase.com

171–180 of 194 posts

Re: Supabase Storage now supports the S3 protocol

#171

Earlier quoted context omitted.

Sure. I wouldn't quite agree with you that "there is nothing missing" though. https://github.com/orgs/supabase/discussions/4444 https://github.com/orgs/supabase/discussions/4421

I believe that the self hosted version is missing auth hooks. https://www.reddit.com/r/Supabase/comments/1bpaq9w/comment/k...

Following...

Re: Supabase Storage now supports the S3 protocol

#173

Cool to see that Supabase is adding S3 protocol! Nice to see more and more storage solutions available. We, at Milvus, I've integrated S3, Parquet and other ones to make it possible for developers to use their data no matter what they use. For those who have used both, how do you find the performance and ease of integration compares between Supabase and other solutions like Milvus that have had these features for som…

Nice. Will check out Milvus.

Re: Supabase Storage now supports the S3 protocol

#174
post #162

Earlier quoted context omitted.

Oriole are joining to work on the OrioleDB postgres extension. That's slightly different to this release: - This: for managing large files in s3 (videos, images, etc). - Oriole: a postgres extension that's a "drop-in replacement" for the default storage engine We also hope that the team can help develop Pluggable Storage in Postgres with the rest of the community. From the blog post[0]: > Pluggable Storage gives deve…

What's the point of acquiring them instead of just sponsering the project? I'm trying to understand supabase's angle here and if this is good or bad news for non-supabase postgres users.

We sponsored/invested in them previously (over half a million USD). The benefit of acquiring is that the team can focus on the technology rather than the business/operations around it.

I hope this is the best outcome for the industry. If there are other postgres companies that would like to use oriole, feel free to reach out. It’s 100% open source and we’d love more design partners

Re: Supabase Storage now supports the S3 protocol

#175

Earlier quoted context omitted.

Sure. I wouldn't quite agree with you that "there is nothing missing" though. https://github.com/orgs/supabase/discussions/4444 https://github.com/orgs/supabase/discussions/4421

I believe that the self hosted version is missing auth hooks. https://www.reddit.com/r/Supabase/comments/1bpaq9w/comment/k...

i believe the docker image ID on the docker-compose hasn’t been updated to the latest stable version. I’ll make a PR later when I’m at my computer (or anyone else is welcome to and I can review/merge)

Re: Supabase Storage now supports the S3 protocol

#176

Is there a formal s3 protocol spec or do these companies try to reverse engineer/feature match what AWS provides?

The S3 API reference [1] is closest to a formal spec there is. The request, response and the error codes are pretty well documented.

[1]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_Operatio...

Re: Supabase Storage now supports the S3 protocol

#177

no feedback on this in particular, but I love supabase. I use it for several projects and it's been great. I was hesitant to use triggers and PG functions initially, but after I got my migrations sorted out, it's been pretty awesome.

Do you manage your functions and triggers through source code? What framework do you use to do that? I like Supabase but it’s desire to default to native pg stuff for a lot of that has kind of steered me away from using it for more complex projects where you need to use sprocs to retrieve data and pgtap to test them, because hiding away business logic in the db like that is viewed as an anti pattern in a lot of organ…

The Supabase CLI [1] provides a way for you to manage functions, triggers and anything else in your Postgres database as a migration. These migrations would be checked into your source control.

You can then take it a step further but opting-in to use Branching [2] to better manage environments. We just opened up the Branching feature to everyone [3].

[1]: https://supabase.com/docs/guides/cli/local-development#datab... [2]: https://supabase.com/docs/guides/platform/branching [3]: https://supabase.com/blog/branching-publicly-available

Re: Supabase Storage now supports the S3 protocol

#178
post #93

Do you support S3 event notifications?

We don't support S3 event notifications directly, but you achieve similar functionality by using Database Webhooks [1]. You can trigger any HTTP endpoint or a Supabase Edge function by adding a trigger to the objects table [3] in the Storage schema.

[1]: https://supabase.com/docs/guides/database/webhooks [2]: https://supabase.com/docs/guides/functions [3]: https://supabase.com/docs/guides/storage/schema/design

Re: Supabase Storage now supports the S3 protocol

#179
post #92

One of the big wins we get from AWS is that you can do things like load structured data files (csv, parquet) from S3 directly in Redshift using SQL queries. https://docs.aws.amazon.com/redshift/latest/dg/t_loading-tab...

This is indeed pretty cool. They also have the `aws_s3` extension [1] for doing the same thing inside Postgres. Unfortunately, the extension isn't open source.

[1]: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_...

Re: Supabase Storage now supports the S3 protocol

#180
post #176

Is there a formal s3 protocol spec or do these companies try to reverse engineer/feature match what AWS provides?

The S3 API reference [1] is closest to a formal spec there is. The request, response and the error codes are pretty well documented. [1]: https://docs.aws.amazon.com/AmazonS3/latest/API/API_Operatio...

Thanks for this. Do you know how are redirects handled?

I searched on that page and didn't find anything but I've seen it mentioned elsewhere that they are catered for but I haven't found any documentation for that.

I'm particularly interested in the temporary ones - 302, 303 and 307.

Post reply on HN