Supabase
Kong Addition/Refactor: Edge Function and Vector MGMT #39717
Replies: 4 comments
|
This issue is being closed as it lacks sufficient context and technical detail to be actionable. The issue appears to be a general complaint about Kong (the admin interface) and edge function management without:
If you have a specific technical issue or bug to report, please create a new issue with:
General feature requests and complaints should be posted in GitHub Discussions instead of the issue tracker. |
|
hi, the management of kong and vector via a ui does not really make much sense, is there an issue with the functions/logs routing? |
no @Ziinc, I meant the addition of this: 
It is extremely cumbersome to manage and deploy edge functions as of now. Have to SSH/FTP/etc to transfer files after locating the proper mount for docker, and then manually restart that singular docker thru the gui/cli and it just takes forever compared to normal Supabase hosted It would be super cool if we could have a hot refresh in the deno / edge function dockers by compartmentalizing the processes in Deno (idk if its a native feature) and just restarting the functions rather than rebooting the entire Deno, closer to manage/hosted Supabase experience. I was super tired when writing this originally, so for the reference to vectors: I forgot that it is managed via the CLI for self hosted (I think) and hosted projects. I thought it would be super cool to be able to manage, create, deploy etc the vector embeddings via a proper GUI in Supabase. I thought they had one while writing this for hosted SB and they don't, oops. But it would be cool to be able to do that. Hope that is more specific. |
|
Hi @rootacc3ss - Thanks for this, I'm going to move as an enhancement discussion. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Chore
I am not considering this a feature addition as we already have the basis; this is more a refactor to Kong.
Describe the chore
Kong needs an addition for the GUI which is management of (genuinely, all features/functions, but at least) Edge Functions. It is HELL managing them with my setup. While I am so grateful that we have an easy Deno manager included in the docker kit for Supabase, actually using it is not fun at all.
Furthermore, management of the vector store/db, function management, etc MUST be added to Kong as we have on the Supabase managed platform as soon as possible for our community.
Additional context
It is unfortunate that Supabase ended up taking the "Open(aka closed)AI" Route and dedicated so much money and specific dev to their own managed service, which many of us cannot afford at scale. I am petitioning the primary maintainers to add what we have when paying for Supabase to our self-hosted platform for the betterment of the users. It's not like most people would switch over because of it -- it's far too technical for most beginner devs, or AI monkeys using Lovable to somehow gross $5k/mo off of shovelwear.
I am happy to come on board as a primary maintainer if provided with the proper internal documentation to help make 1:1 feature appends. I am already writing PRs on my fork of the official Supabase MCP for a "self-hosted" mode (on top of Greg's amazing work), and my current addition for edge functions required an entire SSH workflow, as does normal edge function addition.. There has got to be a better way, and that's, at minimum, the addition
I LOVE YOU TEAM SUPABASE. This software has saved me years of trouble, and I've used it since the beginning. Functionality is super important though, and remaining as one of the few open-source SaaS companies with a paid option who cares about the selfhosters and O.S. itself is even more important.
Regards,
rA
All reactions