Closed mikekuzak closed 11 months ago
I just created a PR #83 where you can find the settings for your local Supabase instance. In the config.toml you can define the API schemas to expose: https://github.com/jorge-menjivar/unSAGED/pull/83/files#diff-56c3d03bfaddf3efa07a4efe3dd767c0ecc36441ffe865ee5865794b066ee2faR10
@sebiweise Where is the [supabase/config.toml] file in the docker setup ? Which container does host that ? Any docker env. variables to set this up ?
The config.toml I´ve linked in the privous comment is just for the supabse-cli to get your development env up and running.
Hmm I'm using the supabase docker self-hosted setup. https://supabase.com/docs/guides/self-hosting/docker
I don´t really know how to configure the expose schema for the docker self hosted version, maybe the Supabase Support can help you? But for the future we are trying to implement the native Supabase auth and/or Clerk so this wont be needed when this feature is implemented, the next_auth schema will be gone then. See #91
Expose the next_auth schema Expose the nextauth schema in the [API settings](https://app.supabase.com/project//settings/api) by adding next_auth to the "Exposed schemas" list.
More information here.
Then copy the output and save it for the next step.
API settings don't exists in the UI in a self hosted instance.