4 ms·

> neutered Can you share more? There is nothing missing, it’s all the same code that we run in production (besides some login changes to keep it decoupled from

> neutered Can you share more? There is nothing missing, it’s all the same code that we run in production (besides some login changes to keep it decoupled from the platform)

ihateolives 3y ago
From top of my head: reports and multiple projects. Also I kept getting weird "fetch failed" errors when creating rules or adding users from gui working behind reverse proxy so I gave up on the end.
replwoacause 3y ago
Sure. I wouldn't quite agree with you that "there is nothing missing" though. https://github.com/orgs/supabase/discussions/4444 https://github.com/orgs/supabase/discussions/4444 https://github.com/orgs/supabase/discussions/4421 https://github.com/orgs/supabase/discussions/4421
- kiwicopple 3y ago
  thanks for the links > https://github.com/orgs/supabase/discussions/4444 https://github.com/orgs/supabase/discussions/4444 This discussion is about configuration: self-hosters configure configure their services in code[0], using .env vars / docker-compose.yml and should be checking it into source control. Self-hosters are not missing any functionality - the opposite actually: we have a subset of configuration items available on the platform I get that it's different to the platform, but it's (IMO) the more "correct" way - all configuration should be version controlled > https://github.com/orgs/supabase/discussions/4421 https://github.com/orgs/supabase/discussions/4421 This one is about Auth providers. They are also configuration: https://github.com/supabase/auth?tab=readme-ov-file#configuration https://github.com/supabase/auth?tab=readme-ov-file#configur... [0] Configuration in code: https://supabase.com/docs/guides/self-hosting/docker#configuring-services https://supabase.com/docs/guides/self-hosting/docker#configu... [1] Terraform: https://supabase.com/docs/guides/platform/terraform https://supabase.com/docs/guides/platform/terraform
  - deleted 3y ago
    [deleted]
  - kiwicopple 3y ago
    (FYI: I saw a deleted comment that this requires a restart: the same is true on the platform)
- tmountain 3y ago
  I believe that the self hosted version is missing auth hooks. https://www.reddit.com/r/Supabase/comments/1bpaq9w/comment/kx3y479/?context=3 https://www.reddit.com/r/Supabase/comments/1bpaq9w/comment/k...
  - asciii 3y ago
    Following...
  - kiwicopple 3y ago
    i believe the docker image ID on the docker-compose hasn’t been updated to the latest stable version. I’ll make a PR later when I’m at my computer (or anyone else is welcome to and I can review/merge)
    - tmountain 3y ago
      Awesome, thanks for following up and for making a great product!
      - kiwicopple 3y ago
        I checked with the team - it was already in the self-hosted version. There are some guides for using this in the CLI docs: https://supabase.com/docs/guides/auth/auth-hooks#local-development https://supabase.com/docs/guides/auth/auth-hooks#local-devel... (I'll find a way to consolidate these docs so the work across CLI + docker-compose)

> neutered Can you share more? There is nothing missing, it’s all the same code that we run in production (besides some login changes to keep it decoupled from the platform)

ihateolives 3y ago

From top of my head: reports and multiple projects. Also I kept getting weird "fetch failed" errors when creating rules or adding users from gui working behind reverse proxy so I gave up on the end.

replwoacause 3y ago

Sure. I wouldn't quite agree with you that "there is nothing missing" though. https://github.com/orgs/supabase/discussions/4444 https://github.com/orgs/supabase/discussions/4444 https://github.com/orgs/supabase/discussions/4421 https://github.com/orgs/supabase/discussions/4421

kiwicopple 3y ago
thanks for the links > https://github.com/orgs/supabase/discussions/4444 https://github.com/orgs/supabase/discussions/4444 This discussion is about configuration: self-hosters configure configure their services in code[0], using .env vars / docker-compose.yml and should be checking it into source control. Self-hosters are not missing any functionality - the opposite actually: we have a subset of configuration items available on the platform I get that it's different to the platform, but it's (IMO) the more "correct" way - all configuration should be version controlled > https://github.com/orgs/supabase/discussions/4421 https://github.com/orgs/supabase/discussions/4421 This one is about Auth providers. They are also configuration: https://github.com/supabase/auth?tab=readme-ov-file#configuration https://github.com/supabase/auth?tab=readme-ov-file#configur... [0] Configuration in code: https://supabase.com/docs/guides/self-hosting/docker#configuring-services https://supabase.com/docs/guides/self-hosting/docker#configu... [1] Terraform: https://supabase.com/docs/guides/platform/terraform https://supabase.com/docs/guides/platform/terraform
- deleted 3y ago
  [deleted]
- kiwicopple 3y ago
  (FYI: I saw a deleted comment that this requires a restart: the same is true on the platform)
tmountain 3y ago
I believe that the self hosted version is missing auth hooks. https://www.reddit.com/r/Supabase/comments/1bpaq9w/comment/kx3y479/?context=3 https://www.reddit.com/r/Supabase/comments/1bpaq9w/comment/k...
- asciii 3y ago
  Following...
- kiwicopple 3y ago
  i believe the docker image ID on the docker-compose hasn’t been updated to the latest stable version. I’ll make a PR later when I’m at my computer (or anyone else is welcome to and I can review/merge)
  - tmountain 3y ago
    Awesome, thanks for following up and for making a great product!
    - kiwicopple 3y ago
      I checked with the team - it was already in the self-hosted version. There are some guides for using this in the CLI docs: https://supabase.com/docs/guides/auth/auth-hooks#local-development https://supabase.com/docs/guides/auth/auth-hooks#local-devel... (I'll find a way to consolidate these docs so the work across CLI + docker-compose)