-
Notifications
You must be signed in to change notification settings - Fork 111
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
Turn off GraphQL server #561
Comments
@faces-of-eth - curious how you get the event data into Supabase itself? if you are considering turning off the grahpql endpoint I assume you have an external service reading ponder db and writing into supabase? or another way? thanks |
Hey! By default Supabase exposes a graphql endpoint (https://supabase.com/docs/guides/graphql), and you can simply point ponder at Supabase via a postgres connection URL. I've moved away from this particular setup and Ponder for the moment in particular because of other things the team is actively working on, but just not quite ready for my needs. Will be back to evaluate in a few versions when it's a bit more mature! |
Sort of piggybacking on Issue 514 I think it might be helpful to turn off the GraphQL server completely for certain people.
Currently I'm using Ponder and Reservoir Light Sync Nodes to dump everything into a Supabase database, then using its built-in GraphQL server so I can query the union of data.
In this setup, the GraphQL server for Ponder doesn't add much benefit for me, and mostly only overhead.
The text was updated successfully, but these errors were encountered: