This is just a feature idea (and perhaps if I have time I'll draw up a PR), but since most folks interacting with Supabase are using Phoenix/Ecto already so it would be nice to configure it with a Repo module and/or database_url rather than a keyword list.
> There are many libcluster adapters already, so what pushed Supabase to make a database backed one? What is the advantage?
usually the strategies are focused on the cloud provider and since we want to keep it adaptable to multiple cloud providers it felt that using one of those strategies would not be the way to go.
another factor was the fact that we already use heavily postgres in all our projects so if that is available to us we should use that instead
also follow up question, is Supabase using one database per "app" (one cluster) or are there a few different elixir apps that are being backed by the same database (multiple independent clusters)? Though I wonder if using the same storage location for multiple clusters conflicts with how libcluster strategies work.
I just saw this in the logs. Not sure what happened. If you have info about the path you took (was it during auth with slack or..?) that'd be super helpful.
I clicked on Add To Slack, chose the channel I want to add it to, click on Allow, and the error comes up. I haven't been able to get past that part. But I'm pretty sure I know why... I'm not an administrator. Just wanted to add this as I work with people in different time zones. I'll ask the admin to add it ;)
Thanks! That confirms what I saw in the logs. I've added a warning message to catch that error and mention admin access is required. Thanks for catching that.
There are many libcluster adapters already, so what pushed Supabase to make a database backed one? What is the advantage?
> Postgres LISTEN and NOTIFY commands with Postgrex
I know Supabase has hooks (https://supabase.com/docs/guides/database/webhooks) so is the hope to leverage that tech to trigger something whenever a new node connects?
---
This is just a feature idea (and perhaps if I have time I'll draw up a PR), but since most folks interacting with Supabase are using Phoenix/Ecto already so it would be nice to configure it with a Repo module and/or database_url rather than a keyword list.