How to create and schedule Edge functions on self hosted Supabase (Docker)?

[Tom-De-Backer]

I have self hosted Supabase via container on a VM. I would like to add some edge functions to this Supabase instance, but there seems to be an issue. I have already added the cron integration, where I am trying to add a new job via this screen:

The first thing that seems not right is: Supabase tells me "No edge functions created yet". However, there is a 'main' and a 'hello' function as an example in the docker github of Supabase. So I assume these functions should have been shown there. However, I try to create a new function but that does not work. The webpage shows a supabase logo that is running forever.

What is going wrong here?
This is the studio version I use: supabase/studio:20241202-71e5240
The functions container in docker-compose.yml looks like this:

  functions:
    container_name: supabase-edge-functions
    image: supabase/edge-runtime:v1.66.4
    restart: unless-stopped
    volumes:
      - ./volumes/functions:/home/deno/functions
    depends_on:
      analytics:
        condition: service_healthy
    environment:
      JWT_SECRET: ${JWT_SECRET}
      SUPABASE_URL: http://kong:8000
      SUPABASE_ANON_KEY: ${ANON_KEY}
      SUPABASE_SERVICE_ROLE_KEY: ${SERVICE_ROLE_KEY}
      SUPABASE_DB_URL: postgresql://postgres:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}
      # TODO: Allow configuring VERIFY_JWT per function. This PR might help: https://github.com/supabase/cli/pull/786
      VERIFY_JWT: "${FUNCTIONS_VERIFY_JWT}"
    command:
      [
        "start",
        "--main-service",
        "/home/deno/functions/main"
      ]

[sscarduzio]

@Tom-De-Backer did you ever solve or work around this successfully?

[clouedoc]

They just don't spend any significant resources on the self-hosted version, on purpose, to make you use the cloud one.
I think it's okay, but it's a bit painful to have to put all the pieces together.

For example:

Cannot Save SQL Snippets
Supabase AI buggy in self-hosted
The official JWT generator tool in the documentation is buggy on purpose (lost two hours -- the solution was to use JWT.io)
Storage requires starting a few more containers (docker-compose.s3.yml)
CRON requires additional setup steps

The more I see undocumented missing features, the more I regret using Supabase in the first place...

[uahic]

they need to make some money of course but I am currently also on the edge - to supabase or to build my own backend? Not sure but I think if using Spring boot it takes some days to set everything up but then you know how it works exactly, no surprises and fully customizable. I have done this before once but hoped to save time using tanstack start + supabase. What I didnt liked is that I have to use their auth server and that security is mostly RLS (high coupling of business logic in the DB, potentially).

[aantti]

@clouedoc Nothing has/had been "buggy on purpose" :) There has been definitely quite a few gaps regarding maintenance and updates, but without any specific intent on making self-hosted Supabase unusable or such. Apologies for any inconveniences you might have experienced. I've recently updated the self-hosting Supabase guide you've referred, as well as adding a utility shell script to generate all secrets and API keys. More work in progress to add support for the new opaque API keys and asymmetric encryption/signing keys.

The SQL snippet editor has also been recently added, as well as the initial support for Edge Functions UI - check the CHANGELOG for more information on updates.

[clouedoc]

@clouedoc Nothing has/had been "buggy on purpose" :)

Hi, yes, for the snarky Hacker News-style comment, I think that I was in a really bad mood that day... My apologies...

The Supabase ship has sailed for me, but I'm glad you are ironing out bugs out of the self-hosted version!

[aantti]

@clouedoc No problem at all :) Thanks, yeah, working on it!

[aantti]

Added a how-to guide about edge functions in self-hosted Supabase :)

https://supabase.com/docs/guides/self-hosting/self-hosted-functions

Hope this helps