Hacker News new | ask | show | jobs
by xrd 1550 days ago
I've been using hasura for a long time and this offering from supabase is the first time I've ever thought I could move away from hasura. Looks simply amazing.

The Gui for adding roles and tying them to postgres access is very slick with hasura. Is this done manually via SQL commands with supabase?

My litmus test will be if I can run the entire solution from docker or if I'll need to assemble the pieces. Hasura is so easy to boot up with a few environment variables, run locally or inside dokku, and that makes it so simple to set up and start building.

1 comments

> entire solution from docker

We PR'd this into our docker-compose today [0]. We're always a bit slammed during Launch Week, so if you spot any problems let use know and we'll patch it up asap.

The extension is also deployed directly into our PG bundle [1] which is available in docker [2]

> The Gui for adding roles and tying them to postgres access is very slick with hasura. Is this done manually via SQL commands with supabase?

pg_graphql works with Postgres Row Level Security - we provide a GUI for this in our Dashboard, but they are also just native PG Policies, so you can write them in raw SQL. (I haven't tried Hasura so I don't know if this is a direct comparison.)

[0] https://github.com/supabase/supabase/pull/6138/files#diff-41...

[1] https://github.com/supabase/postgres

[2] https://hub.docker.com/r/supabase/postgres

The GUI leaves a lot to be desired though. I'm wondering why there is no work being done on just copying what Hasura did with its RLS interface?

I've used it for small projects where permissions are done in an hour of work and big projects with complex permissions were also totally doable, albeit a bit convoluted but that's just complex permissions being convoluted themselves

So why not just copy it and write the "policy" behind the scenes (optionally)?

Thanks for the feedback - sounds like we need to check out the Hasura implementation.

I'll pass that onto the team. We've been planning to re-write the Policy editor for a while now - this feedback is a good justification to prioritize the work.