supabase-kubernetes is in bad shape and feels abandoned
I've got a couple PRs open (#94 #95 #96) for basic fixes that would stop anyone from getting up and running that have been sitting open for months. It's been on my backburner to take a big swing at getting it cleaned up and deployable for an open-source project I use Supabase on and currently self-host just through docker-compose on a VM.
Someone just hit me up and offered to contract me to help them get it up and running. If I'm going to do this I don't want to end up maintaining a fork for me plus them with a dozen tidy PRs sitting in purgatory. What's the process for becoming a maintainer on the official supabase-community repo?
3 Replies
hey @chris out of curiosity (I don't think I have deep enough knowledge to help out) did you get anywhere with this? I agree the helm chart seems to be rotting away a little, and could do with some TLC (the thing that stuck out to me was having a basic action that published the chart on github pages so one could use it without checking it out and fiddling).
no I haven't. It's on my backlog still to get a helm chart cleaned up so I can move one of my Supabase instances from a VM to k8s. I haven't had any luck getting in touch with any maintainers and all the open PRs on the repo seem to be dead in the water so I'll have to fork
No worries 👍 I'd like to use this as well so if you do fork and I'm at that point myself (of expertise+time) I'll happily help out. Will give you a shout once I'm at that point. My interest would be around getting it ready to use in prod likely with some kind of postgres operator like stackgres.