I cannot change any settings from hidden pages, open source?

[miguelgargallo]

When are you going to allow users to access this functionalities coded? when

https://myopensourceurl .app/new/default-org-slug

https://myopensourceurl .app/project/default/auth/templates

https://myopensourceurl .app/new/default-org-slug

https://myopensourceurl .teide.app/project/default/auth/providers

[ryunosuke21]

I agree 100%, I've been so confused on how to do certain things while self hosting. I think better documentation would be a huge step for this issue to be solved.

For anyone who's been having the same issues:

Here are some breadcrumbs I've managed to find:

• Auth Providers: check out this issue. They added some lines to the docker-compose.yml and the .env file. This article also provides good insight on what to do.
• Email Templates: apparently its the same thing about changing stuff in the docker-compose.yml. I'm trying to find any relevant links but so far I haven't been able to so far. Edit: Found the link, its in this discord discussion

Also, this video by activenode is really helpful for some things, but as far as I understand, he's using 2 servers, one for s3 buckets and one for supabase. If you're not using s3 buckets this would still work.

[charislam]

We definitely hear you about improving documentation for local dev and self-hosting. Regarding email templates, you can customize them here: https://supabase.com/docs/guides/cli/customizing-email-templates

[miguelgargallo]

Begin by putting here the hidden pages on the open source version, sidebar and also under policies

[encima]

@miguelgargallo those pages are hidden because they are not all functional. Self-hosted Supabase does not use the Management API and pages are not shown because they do not fully function.

We will leave this issue open as it can help us track the improvement of documentation of the current functionality and setup processes

[miguelgargallo]

No @encima and supabase team, pages are coded, functionalities exist, but because of a commercial thing, I thought this is hidden with the goal to push users to the commercial and not opensource

this is a screenshot from my opensource version, not even 2!

[encima]

@miguelgargallo I understand why you may think that and it is certainly not an uncommon practice.
However, this is not the case here. Pages are not enabled when we cannot guarantee the same experience as we can in the hosted version.
I am not sure what your screenshot is showing but maybe I have missed some context here?

[Hallidayo]

Hi everyone, due to inactivity on this issue I've moved the issue over to discussions/enhancements.

[opxdelwin]

Hey @encima, I'd love to work on this to implement the screen with the available auth providers as of now.

I understand that the team would love to launch this once Everything is functional, but let the self hosted users access what's available, and we can expand the choices from there.

[encima]

You are very welcome to open a PR to expose settings that are available now!

[opxdelwin]

Cool, could you please confirm on the available providers for a reference?