-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Help Needed] - Is a on-prem supabase install supported ? #90
Comments
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: |
@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. |
I don´t really know how to configure the expose schema for the docker self hosted version, maybe the Supabase Support can help you? |
Expose the next_auth schema
Expose the next_auth schema in the API settings 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.
The text was updated successfully, but these errors were encountered: