How to update the rest of the Supabase template after manually upgrading PG to v17

[AmadorSV]

Hey everyone,

I deployed a Supabase stack a while ago using the official Dokploy template back when it defaulted to Postgres 15.

I recently upgraded the database. I went ahead and manually ran the official Supabase upgrade script (utils/upgrade-pg17.sh) inside the volume's directory. The database successfully moved up to Postgres 17, and that part is working fine.

However, the rest of my companion services (Studio, GoTrue, PostgREST, Storage, etc.) are still pinned to the old image tags from that original PG15-era template. I want to bring all those other services up to date with the latest template changes without accidentally breaking anything or screwing up my current PG17 setup.

What is the best way to handle this in Dokploy? Can I just pull the latest template changes, or do I need to manually adjust environment variables or configs so the updated services play nice with the new database?

Also, a quick question regarding backups: I noticed that when Dokploy runs its global backup, it already includes all the Supabase files and volumes. Is relying on Dokploy's built-in volume backup safe enough for a full restore, or should I explicitly set up a separate pg_dump script for the database? I'm mostly worried about things like the pgsodium encryption keys that live in the config volumes.

Any advice or steps on how to handle this safely would be highly appreciated. Thanks!

[Meliceanu]

The Dokploy Supabase template is just a starting docker-compose.yml — once deployed it's an ordinary Compose stack that you own and can edit. There's no separate "update the template" step: you edit the compose of your existing stack in Dokploy, bump the companion image tags, and redeploy.

A few things to make this safe and predictable:

Update to a matched set, not one service at a time. Supabase builds and tests its self-host images together, and newer releases occasionally add required env vars — so don't cherry-pick versions. Take a consistent set from one release. Two good sources:

• Upstream, canonical: supabase/supabase → docker/docker-compose.yml
• Dokploy's own current blueprint (already on PG17): Dokploy/templates → blueprints/supabase/docker-compose.yml — you can diff yours against it.

The current tested set is roughly:

supabase/studio:2026.07.07-sha-a6a04f2
kong/kong:3.9.1
supabase/gotrue:v2.189.0
postgrest/postgrest:v14.12
supabase/realtime:v2.102.3
supabase/storage-api:v1.60.4
supabase/postgres-meta:v0.96.6
supabase/edge-runtime:v1.74.0
supabase/supavisor:2.9.5
darthsim/imgproxy:v3.30.1

The companion services aren't pinned to the Postgres major version. Studio, GoTrue, PostgREST, Storage, meta and realtime all reach Postgres over the connection string, so they already work against your PG17 — updating them is about newer fixes/features, not a requirement of the upgrade itself.

Before redeploying: pull the matching .env from the same release and diff it against yours (that's where newly-required variables show up), and back up the Postgres volume first. Then redeploy the stack from Dokploy.