Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GraphQL is now available on Supabase

supabase.com

Post reply on HN
Print view View original

11–20 of 49 posts

Re: GraphQL is now available on Supabase

#11

Post by andrew_ »

oliverrice wrote: post #8
andrew_ wrote: post #3

Earlier quoted context omitted.

big fan of what you all are doing with this. the one massive need we still have are great user stories and recipes around auth, and some common kinds of things people do with auth, and how it affects mutations, queries, etc. It's all very vague at the moment and the docs don't go into much depth. cheers

If you're an existing supabase customer you don't need to change any of your existing permissions. pg_graphql filters out any tables/columns that aren't accessible to the user making the request. It also respects your row level security policies. If you can't see something in the introspection schema, you'll get a friendly error if you try to access it. pg_graphql does not used any privileged access so the queries ar…

that's great, but what if I want to add a role to my user to do something like send an email with an extended schema (when that lands). What if I'm not familiar with "row level permissions" and I have a SaSS app where different users can access different rows based on column content? Scenarios like those are where the docs fall short. PLEASE think like new users and not like seasoned engineers with prior experience with the feature set.

Re: GraphQL is now available on Supabase

#12

Post by 5Qn8mNbc2FNCiVV »

kiwicopple wrote: post #9
xrd wrote: post #7

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…

> 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 wit…

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)?

Re: GraphQL is now available on Supabase

#14

Post by kiwicopple »

davidkuennen wrote: post #10
kiwicopple wrote: post #2

hey HN, supabase ceo here. I'm really excited about this release. Our GraphQL implementation is built on top of pg_graphql[0], a PostgreSQL extension we open-sourced a few months ago. The implementation works with a lot of native PG functionality (like Row Level Security). You can also do a some neat things with PG GRANTS, enabling/disabling access to different tables/columns to effectively serve a different GraphQL…

Hey, thanks for creating this! It's nice to see more products in that space. Off-Topic: How did you create your blog? It's seems like you developed it yourself? I'm currently contemplating on how to create the blog for my product, since I want to have it integrated into the main website as well (as subdirectory). It's not really possible when using third party providers. You always have to use subdomains there.

Yes we developed it ourselves. It's all open source [0] so feel free to fork and modify for yourself.

Inside that repo you'll see two key folders:

    - web: our Docs (built with Docusaurus)
    - www: our website + blog (built with Next.js)
The naming convention could be better.

Both of these are deployed to Vercel as separate "sites" using their mult-zone setup [1]. This setup is so that the docs are deployed on a sub-path (supabase.com/docs), rather than a subdomain (docs.supabase.com)

[0] https://github.com/supabase/supabase

[1] Vercel multi-zones: https://nextjs.org/docs/advanced-features/multi-zones

Re: GraphQL is now available on Supabase

#15

Post by davidkuennen »

kiwicopple wrote: post #14
davidkuennen wrote: post #10

Earlier quoted context omitted.

Hey, thanks for creating this! It's nice to see more products in that space. Off-Topic: How did you create your blog? It's seems like you developed it yourself? I'm currently contemplating on how to create the blog for my product, since I want to have it integrated into the main website as well (as subdirectory). It's not really possible when using third party providers. You always have to use subdomains there.

Yes we developed it ourselves. It's all open source [0] so feel free to fork and modify for yourself. Inside that repo you'll see two key folders: - web: our Docs (built with Docusaurus) - www: our website + blog (built with Next.js) The naming convention could be better. Both of these are deployed to Vercel as separate "sites" using their mult-zone setup [1]. This setup is so that the docs are deployed on a sub-path…

Wow, thanks. Much appreciated.

Re: GraphQL is now available on Supabase

#16

Post by kiwicopple »

5Qn8mNbc2FNCiVV wrote: post #12
kiwicopple wrote: post #9

Earlier quoted context omitted.

> 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 wit…

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 "po…

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.

Re: GraphQL is now available on Supabase

#17

Post by alx__ »

davidkuennen wrote: post #10
kiwicopple wrote: post #2

hey HN, supabase ceo here. I'm really excited about this release. Our GraphQL implementation is built on top of pg_graphql[0], a PostgreSQL extension we open-sourced a few months ago. The implementation works with a lot of native PG functionality (like Row Level Security). You can also do a some neat things with PG GRANTS, enabling/disabling access to different tables/columns to effectively serve a different GraphQL…

Hey, thanks for creating this! It's nice to see more products in that space. Off-Topic: How did you create your blog? It's seems like you developed it yourself? I'm currently contemplating on how to create the blog for my product, since I want to have it integrated into the main website as well (as subdirectory). It's not really possible when using third party providers. You always have to use subdomains there.

There's several ways to have a blog path contain a separate setup from the marketing/product routes.

One is to run a reverse proxy on the root domain to pull in separate routes for various services.

https://github.com/http-party/node-http-proxy

You can do rewrites at the server level for the root domain

Or if the app on the root domain can do the routing for you (have done this before with a Rails app)

Re: GraphQL is now available on Supabase

#19

Post by tomatowurst »

been curious as to what sort of savings you've been able to get with supabase because we are approaching a few thousand dollars to store a couple terabytes on DynamoDB

Thinking of buying a dedicated server from Hetzner to run Supabase on it instead but worried about latency. awful that we have to move away from AWS for this but with four/five dedicated servers in EU, US-West, US-East, Singapore and Tokyo, we could have a fixed monthly storage/database cost with some globalized latency (client would connect to whichever dedicated server is available).

we realize that we are at complete mercy of AWS as was expected but the database storage cost was a curveball, so much so that we are thinking of self-hosting database ourselves but seems like a daunting task of its own.

tldr: unpredictability and variability of storage size on Dynamodb is forcing us to explore a more reliable fixed cost solution via self-hosting and hardening our dedicated servers running Supabase.

Re: GraphQL is now available on Supabase

#20

Post by nyellin »

n1ru4l wrote: post #4
kiwicopple wrote: post #2

hey HN, supabase ceo here. I'm really excited about this release. Our GraphQL implementation is built on top of pg_graphql[0], a PostgreSQL extension we open-sourced a few months ago. The implementation works with a lot of native PG functionality (like Row Level Security). You can also do a some neat things with PG GRANTS, enabling/disabling access to different tables/columns to effectively serve a different GraphQL…

Had a lot of fun collaborating with you on the supabase pg_graphql example, which of course is a HackerNews clone! https://github.com/supabase-community/supabase-graphql-examp...

You should call it pg_pg
Post reply on HN