Anyone have any suggestion on this error I'm getting with docker? None of the containers are able to access the database during

docker-compose up

even though

supabase-db

is successfully created and started.

onAuthStateChange

Docker issues

Hi everyone, is there any place for discussion surrounding deploying Supabase on Kubernetes? I see the repo is still empty on GitHub

Is there a way to identify which free projects in all my orgs are created by me? It looks like you can only have 2 free projects now, and I'm not sure which projects are being counted against me because all remaining are in shared orgs. Also I deleted one project and am still getting the same error, so I assume I had 3+ but not sure how to see how many there are/which they are

Need help - Syntax error at or near select

Hi everyone 🙂 I'm working a small project with the League of Legends API, learning Supabase as well. I'd like some guidance with auth/Row Level Security. Basically when a player enter their name, it goes to the League API and retrieves the user data and I want to insert it. However when I try it tells me that

new row violates row-level security policy for table "summoners"

. I guess it means it requires auth to go through and get some grants that would allow the write?

Have you defined any policies for that table? The studio provides a few canned policies that can be useful but by default there's no policy so basically you can't do anything with the table 😄

No policies yet. But I'm still figuring out how to deal with the inserts at all. Technically the user shouldn't need to be authed to call the endpoint that will do the insert

So I should remove the RLS entirely?

Then you need to add a policy to allow non authenticated users to do the insert

Ok thanks, will look into it!

In the studio if you go to Authentication > Policies there's a bunch of templates that you can customize and take inspiration from to define your own policies

Thanks a lot! 🙂

There is a concept with RLS that i don't really understand. What if I want everyone to be able to read. Fine, i'll just return true for SELECT. But if I want to restrict all inserts except for requests from my server maybe with a specific auth key or something, how will I do this? This has nothing to do with users och authenticated users, it's just that I want to make sure my server is the only one who can make inserts, not any other user from a rest-client or so. How do I achieve this? Thanks!

Yeah that's definitely the way I feel right now

If it's a request made on your server, just use a service key and it will bypass all RLS restrictions

The key tagged

service_role

secret

@User ?

yep

just make sure never to leak it to the front/client app

Thanks 🙂 And yeah ofc 🙂 cc @User you might find that info helpful

And thanks a lot @User for the info! 🙂

@User Oh of course, that makes sense! I guess need to create a separate supabaseClient instance for the server then? (I'm using Next JS with some code in a api endpoint)

That's an interesting question indeed. I use Nest and created a wrapper that exposes specific function (

selectPlayerByName

). Should I have 2 instances, one for

regular

use, and one for

service

use?

Can i create policies for functions? How can protect it if not?

Function policies

So hmmm... I broke my DB (had some errors with migrations and then was stupid enough to remove the

schema_migrations

table). It's still a dev version so I could reset the db completely. Is there to reset the remote db? I still have the proper migrations on my version control 🙂

Reset database

I am new to Supabase and seeing an error while attempting to use the SQL editor to run a command to define some new tables and relations: I can see the error but there is no line number associated with it. Is there a way to get this information?

And is export off Supabase officially supported?