Hey, I've been using a supabase s3 bucket to upload my images and I've been rendering the images through my API route so far. I decided to turn on disablePayloadAccessControl and render the bucket URL directly instead, and after some trouble, I was able to get it working by parsing the URL with generateFileURL, as described here: https://github.com/payloadcms/payload/discussions/5334#discussioncomment-12010904. Does anyone know if I'm missing something and that's why I need to parse this URL? If I don't implement the generateFileURL function from the s3Storage adapter, I get a URL that looks like this: https://<host>.supabase.co/storage/v1/s3/<bucket-name>/<prefix>/<filename>. If I try to visit this URL on the frontend, I get an accessDenied. The URL that works for me is https://<host>.supabase.co/storage/v1/object/public/<bucket-name>/<prefix>/<filename> (note that I replaced /s3 with /object/public. Does anyone here know why? Or maybe anyone here has an example repo that you can share?
#Supabase S3 Storage bucket - public URLs
ocean cargo
quaint quartzBOT
bitter bluff
I can’t offer help, but I can tell you I had to do the same thing. I only used it for a prototype, though, so I didn’t troubleshoot
We moved to AWS after my POC
ocean cargo
Hey, thanks @bitter bluff . Ok, I won't worry about this one for now then since we'll also move to AWS S3 🙂 . Maybe that's exactly what the plugin does: it builds the URL the AWS way. Thanks!
flint void