[Question] - 401 on access to conversation table in Supabase about unsaged HOT 5 CLOSED

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 #104 (comment)

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

from unsaged.

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.

from unsaged.

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

from unsaged.

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 #104 (comment)

from unsaged.

Resolved with new docker file per #120

from unsaged.