feat(service): update Supabase to current latest versions - #8316

Why this was removed?:

is it necessary to have them? thought its not used and not will be anyway

first two are hardcoded keys, POSTGREST_URL, PGRST_JWT_SECRET, DATABASE_URL - just duplicates of what is set up above, FILE_SIZE_LIMIT - old name, renamed to a UPLOAD_FILE_SIZE_LIMIT, STORAGE_S3_, AWS_ - also duplicates, TENANT_ID, REGION - not needed anymore since issue they are referring to is closed + they are commented anyway, ENABLE_IMAGE_TRANSFORMATION, IMGPROXY_URL - duplicates as well

is it necessary to have them? thought its not used and not will be anyway

first two are hardcoded keys, POSTGREST_URL, PGRST_JWT_SECRET, DATABASE_URL - just duplicates of what is set up above, FILE_SIZE_LIMIT - old name, renamed to a UPLOAD_FILE_SIZE_LIMIT, STORAGE_S3_, AWS_ - also duplicates, TENANT_ID, REGION - not needed anymore since issue they are referring to is closed + they are commented anyway, ENABLE_IMAGE_TRANSFORMATION, IMGPROXY_URL - duplicates as well

I asked it because sometimes people comment out configurations so if someone needs it then they just have to uncomment them. I don't use supabase so don't know if those commented out configs are valid or not

is it necessary to have them? thought its not used and not will be anyway
first two are hardcoded keys, POSTGREST_URL, PGRST_JWT_SECRET, DATABASE_URL - just duplicates of what is set up above, FILE_SIZE_LIMIT - old name, renamed to a UPLOAD_FILE_SIZE_LIMIT, STORAGE_S3_, AWS_ - also duplicates, TENANT_ID, REGION - not needed anymore since issue they are referring to is closed + they are commented anyway, ENABLE_IMAGE_TRANSFORMATION, IMGPROXY_URL - duplicates as well

I asked it because sometimes people comment out configurations so if someone needs it then they just have to uncomment them. I don't use supabase so don't know if those commented out configs are valid or not

there is some commented out things that are necessary (like oauth configuration) indeed, but for this section it is not the case, looks like leftovers from old updates

Compare the current template to yours because it looks like you just copied and pasted the Supabase components, because yes, some of the removed ones are necessary.
Currently, the configuration allows all services to be pre-configured and correctly connected to each other.

Compare the current template to yours because it looks like you just copied and pasted the Supabase components, because yes, some of the removed ones are necessary. Currently, the configuration allows all services to be pre-configured and correctly connected to each other.

clarify what from the removed ones are necessary. I've removed either deprecated or duplicated things that were commented out

Might be good to

1. Just re-add those commented fields and remove them in their own PR to reduce the chances of getting blocked
2. Update the docker images to latest (again), as a lot of these are updated in the supabase docker compose

I'm getting errors when trying to view tables in studio

[
  {
    "expected": "string",
    "code": "invalid_type",
    "path": [
      "message"
    ],
    "message": "Invalid input: expected string, received undefined"
  },
  {
    "expected": "string",
    "code": "invalid_type",
    "path": [
      "code"
    ],
    "message": "Invalid input: expected string, received undefined"
  },
  {
    "expected": "string",
    "code": "invalid_type",
    "path": [
      "formattedError"
    ],
    "message": "Invalid input: expected string, received undefined"
  }
]

Do you have that as well?

I'm getting errors when trying to view tables in studio

[
  {
    "expected": "string",
    "code": "invalid_type",
    "path": [
      "message"
    ],
    "message": "Invalid input: expected string, received undefined"
  },
  {
    "expected": "string",
    "code": "invalid_type",
    "path": [
      "code"
    ],
    "message": "Invalid input: expected string, received undefined"
  },
  {
    "expected": "string",
    "code": "invalid_type",
    "path": [
      "formattedError"
    ],
    "message": "Invalid input: expected string, received undefined"
  }
]

Do you have that as well?

I dont. is it a fresh project or migration?

Fresh install, can't get it to work 🥴

Might be good to

1. Just re-add those commented fields and remove them in their own PR to reduce the chances of getting blocked
2. Update the docker images to latest (again), as a lot of these are updated in the supabase docker compose

replying on this 3rd time - though clarified reasons for all changes after first question - if you want to point on some unnecessary removal - reason it by saying what exact line it is and why it should stay. Otherwise these comments doesnt bring any value because they just state "it was here before, I dont know why, but they probably should stay there"

explaining here line by line removals:

# - ANON_KEY=eyJhbGci...                                                                                                   
# - SERVICE_KEY=eyJhbGci...  

hardcoded jwt tokens

# - DATABASE_URL=postgres://supabase_storage_admin:${SERVICE_PASSWORD_POSTGRES}@...

duplicate

# - FILE_SIZE_LIMIT=52428800
duplicate and deprecated - there is a UPLOAD_FILE_SIZE_LIMIT already above

# - STORAGE_BACKEND=s3
# - STORAGE_S3_BUCKET=stub
# - STORAGE_S3_ENDPOINT=http://supabase-minio:9000
# - STORAGE_S3_PROTOCOL=http
# - STORAGE_S3_REGION=stub
# - STORAGE_S3_FORCE_PATH_STYLE=true
# - AWS_ACCESS_KEY_ID=${SERVICE_USER_MINIO}
# - AWS_SECRET_ACCESS_KEY=${SERVICE_PASSWORD_MINIO}
# - AWS_DEFAULT_REGION=stub

duplicates

# - FILE_STORAGE_BACKEND_PATH=/var/lib/storage
duplicated

# - TENANT_ID=stub
# - REGION=stub

these are actually used in official template, will uncomment them and return via env

# - ENABLE_IMAGE_TRANSFORMATION=true
# - IMGPROXY_URL=http://imgproxy:8080

duplicates

regarding second part of the comment - yep, I will pull the latest images and will also add ANON_KEY, SERVICE_KEY, POSTGREST_URL, PGRST_JWT_SECRET since they exist in the official compose

Fresh install, can't get it to work 🥴

will check

Fresh install, can't get it to work 🥴

added some changes and updated images, spinned up fresh next instance and it is working. feel free to test updated version

also adjusted vector changes with the official supabase adapted for Coolify's with starts_with()

Ok this bangs, set it up with no errors after flushing the services json in the coolify docker 👍

hey @andrasbacsai can you please review and merge this pr if all good? 🙏🏻

Yeah would love this latest update. Can you install services on Coolify via PR?

Using this as a base for some testing (excellent work, Vadko <3), it appears potentially possible to update to even newer versions. Newer versions are highlighted in bold.

Supabase Kong (kong:2.8.5)
Supabase Studio (supabase/studio:2026.03.16-sha-5528817)
Supabase Analytics (supabase/logflare:1.31.2)
Supabase Vector (timberio/vector:0.53.0-alpine)
Supabase Rest (postgrest/postgrest:v14.6)
Supabase Auth (supabase/gotrue:v2.186.0)
Realtime (supabase/realtime:v2.76.5)
Supabase Minio (ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z)
Supabase Storage (supabase/storage-api:v1.44.2)
Imgproxy (darthsim/imgproxy:v3.31.1)
Supabase Meta (supabase/postgres-meta:v0.95.2)
Supabase Edge Functions (supabase/edge-runtime:v1.71.2)
Supabase Supavisor (supabase/supavisor:2.7.4)
Supabase Db (supabase/postgres:15.8.1.085)

Kong v3 which is now used by Supabase doesn't work without some config changes - I might give that a go soon.

Using this as a base for some testing (excellent work, Vadko <3), it appears potentially possible to update to even newer versions. Newer versions are highlighted in bold.

Supabase Kong (kong:2.8.5) Supabase Studio (supabase/studio:2026.03.16-sha-5528817) Supabase Analytics (supabase/logflare:1.31.2) Supabase Vector (timberio/vector:0.53.0-alpine) Supabase Rest (postgrest/postgrest:v14.6) Supabase Auth (supabase/gotrue:v2.186.0) Realtime (supabase/realtime:v2.76.5) Supabase Minio (ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z) Supabase Storage (supabase/storage-api:v1.44.2) Imgproxy (darthsim/imgproxy:v3.31.1) Supabase Meta (supabase/postgres-meta:v0.95.2) Supabase Edge Functions (supabase/edge-runtime:v1.71.2) Supabase Supavisor (supabase/supavisor:2.7.4) Supabase Db (supabase/postgres:15.8.1.085)

Kong v3 which is now used by Supabase doesn't work without some config changes - I might give that a go soon.

You have tested these yourself?

Hi @Vadko! 👋

It appears to us that you are either adding a new service or making changes to an existing one.
We kindly ask you to also review and update the Coolify Documentation to include this new service or it's new configuration needs.
This will help ensure that our documentation remains accurate and up-to-date for all users.

Coolify Docs Repository: https://github.com/coollabsio/coolify-docs
How to Contribute a new Service to the Docs: https://coolify.io/docs/get-started/contribute/service#adding-a-new-service-template-to-the-coolify-documentation

potentially possible to update to even newer versions. Newer versions are highlighted in bold.
Supabase Kong (kong:2.8.5)
Supabase Studio (supabase/studio:2026.03.16-sha-5528817)
Supabase Analytics (supabase/logflare:1.31.2)
Supabase Vector (timberio/vector:0.53.0-alpine)
Supabase Rest (postgrest/postgrest:v14.6)
Supabase Auth (supabase/gotrue:v2.186.0)
Realtime (supabase/realtime:v2.76.5)
Supabase Minio (ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z)
Supabase Storage (supabase/storage-api:v1.44.2)
Imgproxy (darthsim/imgproxy:v3.31.1)
Supabase Meta (supabase/postgres-meta:v0.95.2)
Supabase Edge Functions (supabase/edge-runtime:v1.71.2)
Supabase Supavisor (supabase/supavisor:2.7.4)
Supabase Db (supabase/postgres:15.8.1.085)

@Vadko are you going to pick this up?

potentially possible to update to even newer versions. Newer versions are highlighted in bold.

Supabase Kong (kong:2.8.5)

Supabase Studio (supabase/studio:2026.03.16-sha-5528817)

Supabase Analytics (supabase/logflare:1.31.2)

Supabase Vector (timberio/vector:0.53.0-alpine)

Supabase Rest (postgrest/postgrest:v14.6)

Supabase Auth (supabase/gotrue:v2.186.0)

Realtime (supabase/realtime:v2.76.5)

Supabase Minio (ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z)

Supabase Storage (supabase/storage-api:v1.44.2)

Imgproxy (darthsim/imgproxy:v3.31.1)

Supabase Meta (supabase/postgres-meta:v0.95.2)

Supabase Edge Functions (supabase/edge-runtime:v1.71.2)

Supabase Supavisor (supabase/supavisor:2.7.4)

Supabase Db (supabase/postgres:15.8.1.085)

@Vadko are you going to pick this up?

It depends on when this will be merged, because I already updated dependencies several times, I dont want to end up making several more updates again. If a maintainer will reply regarding possibility to merge this I will do final versions review.

updated the templates to the latest versions according to Supabase GitHub, fixed the problem with the logs that @Revadike wrote about, also added a certificate to supabase-supavisor. Encourage everyone who were testing changes previously to do it again, on my side (dev and prod coolify builds) it works. cc @ShadowArcanist

One thing I noticed is that Supabase now make Kong wait for studio to be healthy and not analytics. Don't believe it makes a realistic difference either way.

Trying the new deploy yml. The vector issue came back:

2026-Apr-02 20:34:53 2026-04-02T20:34:53.311617Z INFO vector::app: Log level is enabled. level="info"
2026-Apr-02 20:34:53 2026-04-02T20:34:53.312474Z INFO vector::app: Loading configs. paths=["/etc/vector/vector.yml"]
2026-Apr-02 20:34:53 2026-04-02T20:34:53.328080Z WARN vector::config::loading: Transform "router._unmatched" has no consumers
2026-Apr-02 20:34:53 2026-04-02T20:34:53.328761Z INFO source{component_kind="source" component_id=docker_host component_type=docker_logs}: vector::sources::docker_logs: Capturing logs from now on. now=2026-04-02T20:34:53.328670095+00:00
2026-Apr-02 20:34:53 2026-04-02T20:34:53.328894Z INFO source{component_kind="source" component_id=docker_host component_type=docker_logs}: vector::sources::docker_logs: Listening to docker log events.
2026-Apr-02 20:34:53 2026-04-02T20:34:53.543326Z ERROR vector::topology::builder: Configuration error. error=Transform "rest_logs":
2026-Apr-02 20:34:53 error[E105]: call to undefined function
2026-Apr-02 20:34:53 ┌─ :4:18
2026-Apr-02 20:34:53 │
2026-Apr-02 20:34:53 4 │ .timestamp = to_timestamp!(parsed.time)
2026-Apr-02 20:34:53 │ ^^^^^^^^^^^^
2026-Apr-02 20:34:53 │ │
2026-Apr-02 20:34:53 │ undefined function
2026-Apr-02 20:34:53 │ did you mean "is_timestamp"?
2026-Apr-02 20:34:53 │
2026-Apr-02 20:34:53 = learn more about error code 105 at https://errors.vrl.dev/105
2026-Apr-02 20:34:53 = see language documentation at https://vrl.dev
2026-Apr-02 20:34:53 = try your code in the VRL REPL, learn more at https://vrl.dev/examples
2026-Apr-02 20:34:53 internal_log_rate_limit=false

Aaah, I see. I believe it's because Persistent Storages don't update. Here I see the old version.

Trying the new deploy yml. The vector issue came back

this is likely not related to the changes, since updated vector.yml includes updated parse_timestamp function. There could be various reasons why your coolify uses old file, if its your production coolify, you can update it manually via ssh, if you are testing locally you can spin new docker container.

idk what to do my whole deployment is fucked and im getting such a headache

idk what to do my whole deployment is fucked and im getting such a headache

just update files manually via ssh to the newer versions

How can I do that?

sorry for being off-topic, but the issue right now that I'm struggling with is actually supabase edge functions
I've overwritten the main function and i can't for the life of me get it to work again, even though I put everything back how it was

2026-Apr-02 21:14:29 worker boot error: failed to bootstrap runtime: No such file or directory (os error 2)
2026-Apr-02 21:14:29 Error: main worker boot error
2026-Apr-02 21:14:29
2026-Apr-02 21:14:29 Caused by:
2026-Apr-02 21:14:29 0: worker boot error
2026-Apr-02 21:14:29 1: failed to bootstrap runtime
2026-Apr-02 21:14:29 2: No such file or directory (os error 2)

/data/coolify/services/j13b0ql982u91w50tdgx8b51/volumes/functions# ls -l main
total 8
-rwxrwxr-x+ 1 root root 4841 Apr 2 21:00 index.ts

How can I do that?

sorry for being off-topic, but the issue right now that I'm struggling with is actually supabase edge functions I've overwritten the main function and i can't for the life of me get it to work again, even though I put everything back how it was

2026-Apr-02 21:14:29 worker boot error: failed to bootstrap runtime: No such file or directory (os error 2) 2026-Apr-02 21:14:29 Error: main worker boot error 2026-Apr-02 21:14:29 2026-Apr-02 21:14:29 Caused by: 2026-Apr-02 21:14:29 0: worker boot error 2026-Apr-02 21:14:29 1: failed to bootstrap runtime 2026-Apr-02 21:14:29 2: No such file or directory (os error 2)

/data/coolify/services/j13b0ql982u91w50tdgx8b51/volumes/functions# ls -l main total 8 -rwxrwxr-x+ 1 root root 4841 Apr 2 21:00 index.ts

its because this file was mounted as a directory. You need to delete directory and make sure only file is left

So far it works from what I've tested. I tested using a totally fresh instance and then imported a db backup from file.

Guess there will be some issues with the JWT keys and the new key format in future as they are changing from the current setup although it says it will remain backwards compatible.

many hours laters... the edge functions issue was.... deno.lock. Removing that from root functions folder fixed everything.

BTW, for future testers: Make sure to deploy resource via custom docker file. Don't choose supabase!

So far it works from what I've tested. I tested using a totally fresh instance and then imported a db backup from file.

Guess there will be some issues with the JWT keys and the new key format in future as they are changing from the current setup although it says it will remain backwards compatible.

How did you make a backup? I tried to do this with a coolify postgres backup (.dmp file), but I keep getting errors related to roles. Maybe roles/grants aren't dumped or restored properly?

The template works fine for me, and I have notified core devs so Andras or Peak will merge this one when they have some time

So far it works from what I've tested. I tested using a totally fresh instance and then imported a db backup from file.
Guess there will be some issues with the JWT keys and the new key format in future as they are changing from the current setup although it says it will remain backwards compatible.

How did you make a backup? I tried to do this with a coolify postgres backup (.dmp file), but I keep getting errors related to roles. Maybe roles/grants aren't dumped or restored properly?

I just used the Coolify backup option shown as Superbase DB in the instance settings. I initially setup an s3 service but realised I didnt need that to keep backups (oh well, I now have a Seaweed instance to use for s3 stuff lol). I just downloaded the .dmp from the Coolify ui and then reuploaded to the new instance via the import backup option. The database was just the bare bones structure, some default data, RLS settings and functions. There was no auth users in the table at the time.

So far it works from what I've tested. I tested using a totally fresh instance and then imported a db backup from file.
Guess there will be some issues with the JWT keys and the new key format in future as they are changing from the current setup although it says it will remain backwards compatible.

How did you make a backup? I tried to do this with a coolify postgres backup (.dmp file), but I keep getting errors related to roles. Maybe roles/grants aren't dumped or restored properly?

I just used the Coolify backup option shown as Superbase DB in the instance settings. I initially setup an s3 service but realised I didnt need that to keep backups (oh well, I now have a Seaweed instance to use for s3 stuff lol). I just downloaded the .dmp from the Coolify ui and then reuploaded to the new instance via the import backup option. The database was just the bare bones structure, some default data, RLS settings and functions. There was no auth users in the table at the time.

ah that explains it, these issues were related to auth and storage schema tables not having the proper roles/grants.

This might need updating to add the fix in #9079 - I only discovered that after fixing it myself when Supabase was sending out emails with the internal Kong urls.

Thank you for the PR! 💜

Btw, managed supabase was already on postgresql 17, how come selfhost is still on 15?

Edit:
Ah, I suppose it's because they haven't updated it themselves yet:
https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml

Just fyi if you do want the even newer supabase after this commit, you can just update the docker compose to update the version numbers to match the one on Supabase's compose. It works without issue.