feat: updated supabase versions and required config

[mattias-wiberg]

According to current state of https://github.com/supabase/supabase/tree/master/docker

Verified that all tests passed bby running https://github.com/supabase/supabase/blob/master/docker/tests/test-self-hosted.sh after base64 import to dokploy.

What is this PR about?

Updated the versions of supabase images and adjusted the config accordingly

Checklist

Before submitting this PR, please make sure that:

• I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
• I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
• I have added tests that demonstrate that my correction works or that my new feature works.

Issues related (if applicable)

Close automatically the related issues using the keywords: closes #ISSUE_NUMBER

Screenshots or Videos

Greptile Summary

This PR syncs the Supabase blueprint with the upstream supabase/supabase docker configuration, upgrading all service image versions (studio, kong, auth, rest, realtime, storage, analytics, db, vector, supavisor, etc.) and aligning environment variables, healthchecks, and entrypoints accordingly. The template.toml is substantially expanded with new variables (PG_META_CRYPTO_KEY, Logflare tokens, S3 keys, asymmetric JWT placeholders, POOLER_DB_POOL_SIZE) and improved inline documentation.

Confidence Score: 5/5

Safe to merge; all findings are minor style/convention issues that do not affect runtime behaviour.

Both findings are P2: the networks block violates the project's AGENTS.md convention (Dokploy manages networking) and the meta.json version string was not bumped. Neither blocks functionality — the author confirmed the template works end-to-end against the upstream test script. No logic errors or security issues were found.

blueprints/supabase/docker-compose.yml (networks block on kong), meta.json (version string for supabase entry)

Comments Outside Diff (1)

1. blueprints/supabase/template.toml, line 1 (link)

   meta.json version not updated

   The AGENTS.md convention requires that the version field in meta.json must match the Docker image versions in docker-compose.yml. The current meta.json entry for supabase still shows "version": "1.25.04 / dokploy >= 0.22.5", but this PR bumps multiple service images to versions dated April 2026 (e.g., supabase/studio:2026.04.08-sha-205cbe7). The version string should be updated accordingly (e.g., "1.26.04 / dokploy >= 0.22.5").

   Context Used: AGENTS.md (source)

_{Reviews (1): Last reviewed commit: "feat: updated supabase versions and requ..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

Context used:

• Context used - AGENTS.md (source)

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	a0883dc

[mattias-wiberg]

I assume that check failing since of Service 'studio': Found 'container_name' field. According to README, container_name should not be used. Dokploy manages container names automatically can be ignored as previously done since the names are required in the mounted volumes and need to be static.

[rossanodr]

I assume that check failing since of Service 'studio': Found 'container_name' field. According to README, container_name should not be used. Dokploy manages container names automatically can be ignored as previously done since the names are required in the mounted volumes and need to be static.

sorry I'm new to dokploy.
how can I use this updated version?

[mattias-wiberg]

I assume that check failing since of Service 'studio': Found 'container_name' field. According to README, container_name should not be used. Dokploy manages container names automatically can be ignored as previously done since the names are required in the mounted volumes and need to be static.

sorry I'm new to dokploy. how can I use this updated version?

You can visit the preview site and copy the base64 into a new docker compose.