[Question] - 401 on access to conversation table in Supabase

jorge-menjivar / unsaged

Open source chat kit engineered for seamless interaction with AI models.

https://unsaged.com

Apache License 2.0

248 stars 77 forks source link

[Question] - 401 on access to conversation table in Supabase #98

Closed mikekuzak closed 10 months ago

mikekuzak commented 11 months ago

Hi,

I'm using a docker self-hosted install of supabase. have done the setup, created a user with email address in supabase and connected unsaged with all the Keys to the supabase instance.

I can login via email authentication, will get redirected back to unsaged and I'm getting a black screen. It looks like I'm getting a 401 on trying to get to the conversation resource.

Do I need to assign the supabase user to these tables, or maybe there needs to be an project API key defined in the unsaged config ?

I used the generation script https://github.com/jorge-menjivar/unSAGED/blob/dev/packages/unsaged/db/GenerationScript.sql via the SQL Editor.

Thanks for any advise.

daniel-farina commented 11 months ago

Do you want to try this PR https://github.com/jorge-menjivar/unSAGED/pull/97 ? would love some feedback.

It replaces next-auth with supabase-auth and makes the setup a lot easier, no jw tokens needed and the magic link should work out of the box.

daniel-farina commented 11 months ago

also make sure you .env has the right parameters for supabase on the error your mentioned earlier.

mikekuzak commented 11 months ago

Do you want to try this PR #97 ? would love some feedback.

It replaces next-auth with supabase-auth and makes the setup a lot easier, no jw tokens needed and the magic link should work out of the box.

Yeah sure .. but I need a working unsaged container first. The current Dockerfile is not working.

          Yes thats correct, I think the docker file needs to be updates to pnpm and also adapted to the new turbo repo structure.

Originally posted by @sebiweise in https://github.com/jorge-menjivar/unsaged/issues/104#issuecomment-1824574726

sebiweise commented 11 months ago

Do you want to try this PR #97 ? would love some feedback.

It replaces next-auth with supabase-auth and makes the setup a lot easier, no jw tokens needed and the magic link should work out of the box.

Yeah sure .. but I need a working unsaged container first. The current Dockerfile is not working.
          Yes thats correct, I think the docker file needs to be updates to pnpm and also adapted to the new turbo repo structure.
Originally posted by @sebiweise in https://github.com/jorge-menjivar/unsaged/issues/104#issuecomment-1824574726

I will have a look at the dockerfile tomorrow and I will try to fix it as soon as possible.

Bortus-AI commented 10 months ago

Resolved with new docker file per #120