The previous merge of origin/canary into this branch was committed with
unresolved conflict markers in docker-compose.yml and template.toml,
producing invalid YAML/TOML. It also carried over the old kong
eval-based entrypoint, which made the kong container unhealthy and
failed the deploy (dependency kong failed to start).
This commit restores the known-good template structure from canary
(kong-entrypoint.sh, declarative kong.yml with JWKS/asymmetric key
routes, vector + analytics stack, correct domains) and applies only
the version bumps intended by this PR:
- studio 2026.04.27 -> 2026.06.03-sha-0bca601
- gotrue v2.186.0 -> v2.189.0
- postgrest v14.8 -> v14.12
- realtime v2.76.5 -> v2.102.3
- storage-api v1.48.26 -> v1.60.4
- postgres-meta v0.96.3 -> v0.96.6
- edge-runtime v1.71.2 -> v1.74.0
- postgres 15.8.1.085 -> 17.6.1.136
- supavisor 2.7.4 -> 2.9.5
Deploy-tested on Dokploy: all 13 containers running, kong healthy,
studio dashboard reachable through kong (HTTP 200).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Update Supabase Docker configuration and template
- Updated Supabase Studio and GoTrue images to the latest versions.
- Modified healthcheck commands for the Studio service.
- Enhanced environment variable configuration in docker-compose.yml for better flexibility.
- Updated Logflare API key references and added new S3 protocol access keys in template.toml.
- Introduced custom entrypoint script for Kong to handle Lua expressions and environment variable substitution.
- Added new routes and plugins for enhanced authentication and authorization in Kong configuration.
* Refactor Supabase Docker Compose and Template Configuration
- Removed container name prefixes from services in docker-compose.yml for consistency.
- Increased healthcheck retries and start periods for several services to improve stability.
- Updated healthcheck timeout and retry configurations for the analytics service.
- Adjusted appname generation logic in template.toml to ensure proper naming for services.
- Cleaned up commented sections in template.toml for clarity.
* ⬆️ Update Supabase template to version 1.25.03
* 🐛 Fix url in mail pointing to kong
* ✨ Use new jwt helpers to generate unique jwts
* 📝 Update README to reflect new changes in helpers
- related PR on dokploy https://github.com/Dokploy/dokploy/pull/1749
* ✨ Add pre0.21.8 version of supabase template + use jwt generation in newer template
* 🔧 Add field dokploy_version for supabase templates
* ⬆️ Update supabase version to 1.25.04 for dokploy >=0.1.28
* 🐛 Fix logs in supabase by adding dynamic container names and modifying vector.yml
* ⬆️ Backport supabase 1.25.04 for dokploy < 0.21.8
* 📝 Add link to supabase self-hosting documentation in env file
* 🚚 Change container_name_prefix to include appName
* Update blueprints/pre0.21.8-supabase/template.toml
* Update blueprints/supabase/template.toml
* 🐛 Fix template using appname in older version of template
---------
Co-authored-by: Mauricio Siu <47042324+Siumauricio@users.noreply.github.com>
