Is the storage api supposed to work for local development? I'm getting an RLS policy error when I try to upload files

Hello @Kasper! This thread has been automatically created from your message in #843999948717555735 a ``few seconds ago``. Pinging @User so that they see this as well! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ... menu) and select Leave Thread to unsubscribe from future updates. Want to change the title? Use the

/title

command! We have solved your problem? Click the button below to archive it.

By local development are you are running supabase server yourself, or running code from localhost? Have you set up storage policies for objects in that bucket for insert?

Kasper (2022-03-30)

I'm running the Supabase CLI, followed the Local Development guide so the local database should be the same as the remote

Have you set up storage policies for objects?

Yes

It looks like it's for the other way around, when migrating a storage policy to the remote, but maybe it's the same culprit

Sorry, but I just have not messed with it. I know it is a "fake" storage system locally (not s3) but not clear on policies. No one had responded to you so was trying to get you somewhere, but afraid I might confuse things if I push more. If you narrow down you might ask again as doubt others will drift in to this "older" thread...

Yea I see, thank you for taking the time to respond :)

Try set to just true to see if that works.

Will try that

Local Studio does not have a storage section yet, I believe correct? I can see policies from my datagrip database tool on tables, I don't know the sql off hand to get them. pgadmin supposedly can lisi them.

I tried just disabling RLS for the

storage.objects

table, so now the issue is that the bucket doesn't exist

Well.... In looking at createBucket code it only appears to create the entry in the bucket table in storage schema. Does not make a call to actual storage. So If I read it correctly you can just create a row in the storage table.... https://github.com/supabase/storage-api/blob/master/src/routes/bucket/createBucket.ts

Alright, so you could safely just create the row in the

storage.buckets

table

Even better.

Request to

http://localhost:54321/storage/v1/bucket

body:

{
  "id": "bucket-name",
  "name": "bucket-name",
  "public": true
}

The name bucket is somewhat misleading, as there really are no individual buckets in the s3 sense in Supabase. They have many users in the same s3 bucket.

Including in production as well?

There is no s3 at all in local, just simulated. Everything in the actual storage system is just objects with paths (the Supabase bucket is just part of the path in the actual storage. But it makes it easier for policies like public to have the bucket table.

Yeah, that makes sense

All that and did not solve the original problem, but at least steps forward...

Yeah, better than nothing