am i doing something wrong?

might be helpful https://supabase.io/docs/guides/auth/managing-user-data

Is there a way to check if a user is logged in from a nodejs microservice?

I need access to an external api but accessing it in the react app that uses supabase would expose my external api's key so I'm building a microservice for it. I just need to know if there is a way to check if the user who made the request from the react app -> microservice is logged in.

Can we use StackOverflow for questions that might help others? It's easier to find answers there than here in the chat :(

Is it possible to change the database URL (https://rAnDoMsTrInG.supabase.co )? When a user logs in via Google it references the random URL, which to the untrained eye looks sketchy.

Or perhaps, in Google, a way to control the domain name on the auth consent screen?

I'm having issues with the auto uuid, now is not working when creating new tables with the UI, anyone having the same problem?

It also does not allow me as before to select this option with the UI

It is assigning by default the NULL value for the uuid type, if someone has this same problem using the UI, you can solve it like this:

ALTER TABLE columns_name ALTER COLUMN id SET DEFAULT uuid_generate_v4();

Hey

I would like to know what the key plus the chain symbol mean?

Maybe provide a screenshot of it?

It's in a column

I understand the chain is a foregin relationship

Key = primary key. Link = linked to another table.

Right, what I imagined, but I have these 2 symbols in columns that are not primary keys but only foreign keys

It only happens in this exact table

🤔 Quick Row-level Security question –

1. I enabled RLS for a particular table and set an INSERT policy to

(role() = 'authenticated':: text)

2. In my JS app, I authenticate my user, then click a button to fire off a request to insert a row into that table. 3. Supabase responds with a

403

and this payload:

{"hint":null,"message":"new row violates row-level security policy for table \"settings\"","code":"42501","details":null}

-- ☑️ Troubleshooting I've done: • If I turn off RLS, I can insert a row without a problem. • I have verified that my user is authenticated & has a session by calling the

supabase.auth.session()

&

supabase.auth.user()

methods that the JS client provides. • If I look at the request headers, I can see that the

apikey

and

authorization

headers are being included. --

Does anybody have a suggestion for what else I can try to debug this? Thanks in advance for any tips! 🙌

you can do one of two things: 1) add a SELECT policy as well, since the query right now by default returns the inserted row, it requires SELECT permission 2) set

returning: minimal

in your supabase query, so that the row is inserted but not returned

Ah! Makes sense

Thanks a lot for the tip! 👍🏼

I was having the same exact problem today 😄

hey everyone ! hope you doing well I am building an app using supabase and putting my project on github, my .env that contain the url and anon key is gitignore to be sure, however I am using github actions to automate some task like building the app and uploading it to a gh-pages branch to try out, my problem is : since I don't put the .env file to github, github actions do have access to the keys and therefore when github action build the app there is no connection to the api I tried putting a 'secrets' key on github and referencing it with VITE_SUPABASE_URL= ${{ secrets.VITE_SUPABASE_URL }} but it doesn't seem to work does anybody have any clues on how I can achieve that ? thanks

Or is there a risk to upload url and anon key to a public repo ?

quite unsure on how to use the storage bucket policies, how would I force a size restriction on an avatar uploaded?