I'm not sure that's true. I use storage with a self-hosted instance. It's just the storage isn't backed by S3 by default, its using the FS.

On my self-hosted Supabase project here's all I have:

right.

thank you

While fixing an issue in the SupaBase repo, it's hard to know whether that particular issue has been taken by someone or is yet to fix. Any way to know the status of the issue?

Right, I don’t use the studio UI much for self hosted

oh okay

There is a storage table, with entries and a docker volume with the files that get uploaded

yeah. I saw those after I posted the message

Hi! I don't understand something with Supabase. Since the connection can be made with JS, if people check your project with the dev tools they will be able to see the key and address of your db so they will be able to do something on it no ?

Magic link emails not getting sent for anyone else?

yes, they can see the anon key that can be used to query public data. there is a system of rpc functions and RLS that can be used to prevent access to resources that you want private

How do I change the URL that shows to the user on Google Sign In?

Oooh, this seems so promising, thanks a ton!

I'll try it asap

Does anyone know when login support for the CLI is going to land? Or does anyone have recommendations for keeping multiple supabase "environments" (staging, dev, prod) in sync?

Is there a way to redirect magic link back to the URL it came from?

Hi all! I'm currently struggling with RLS and policies. I basically want to restrict non-admin users from

inserting

,

updating

and

deleting

entities. For this, I created policies on my table with a simple rule:

false

. I changed the role for an admin user to

service_role

to bypass the RLS. Now, when I'm running my integration tests the admin user is allowed to modify entities. The non-admin user is not allowed to

insert

, however

updating

and

deleting

still works. What am I missing?

is there a way to switch the organization of your project?

Merry Christmas everyone!

Hey! Does anyone know if there is a way to create a folder in a storage bucket using sql. I want for example to create a folder for each newly created users.

i think this is what the supabase ui does when you click on the add folder button, judging from the storage table. then u have to add the owner id column for the new user

Its seems to be working, but i wonder how the folder is created in S3 when running this query. I guess supabase has some sort of trigger on the storage.objects table?

i think so too, but i don't really know the details of the supabase internals yet

For S3, there is no real folder. You can just upload an object directly with any "/"s inside the key name, any this simulates folder paths.

Yes i know, but i wonder if when i run my insert query on storage.objects, an empty file is uploaded to S3.

I dont see this trigger in Database > Triggers