github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-11-08 02:09:55 -06:00
Code Issues 3.0k Packages Projects Releases Wiki Activity

[PR #721] [CLOSED] Update Supabase 1.26.01 #7953

New Issue
Closed
opened 2026-05-21 23:26:14 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-21 23:26:14 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/721
Author: @jdjimenez2312
Created: 2/21/2026
Status: ❌ Closed

Base: canary ← Head: Update-Supabase

📝 Commits (7)

  • 6fd70d0 Update Supabase 1.26.01
  • eee9bb3 fix: correct syntax errors in template.toml for the logflare_public and logflare_private keys
  • 5afdc7d fix: update comments for clarity in docker-compose.yml and template.toml
  • 0390d5c feat: add logflare_api_key variable and update env configuration
  • ffe08c0 fix: add missing comma in GOOGLE_PROJECT_NUMBER assignment in template.toml
  • 238a017 fix: update volume paths
  • 55c4db2 fix: update realtime container name

📊 Changes

3 files changed (+156 additions, -96 deletions)

View changed files

📝 blueprints/supabase/docker-compose.yml (+58 -54)
📝 blueprints/supabase/template.toml (+97 -41)
📝 meta.json (+1 -1)

📄 Description

What is this PR about?

New PR of Supabase is updated according to the original .yml and configured to allow multiple instances.

Checklist

Before submitting this PR, please make sure that:

Greptile Summary

Updates Supabase template from version 1.25.04 to 1.26.01 with multiple component version upgrades and configuration improvements. The PR includes changes to support multiple Supabase instances and aligns with the upstream Supabase docker-compose configuration.

Critical Issues Found:

  • TOML syntax errors with missing closing quotes on lines 5-6 will prevent template parsing
  • Realtime service routing is broken - Kong URLs don't match the renamed container (lines 331, 351)
  • Vector logging configuration uses hardcoded container name instead of variable, breaking multi-instance support (line 844)

Notable Changes:

  • Updated 10+ service versions (studio, auth, rest, realtime, storage, imgproxy, meta, functions, analytics, db, vector, supavisor)
  • Changed storage volume paths from ../files/volumes/storage to ./volumes/storage for consistency
  • Added new environment variables for storage S3 protocol configuration
  • Improved logging configuration with updated retry strategies
  • Added new volumes for snippets and edge functions management in studio service

Confidence Score: 1/5

  • This PR has critical syntax and logic errors that will prevent Supabase from functioning
  • Multiple critical issues prevent this from working: (1) TOML syntax errors on lines 5-6 will cause template parsing to fail entirely, (2) Kong routing configuration has incorrect URLs that don't match the renamed realtime container, causing routing failures, (3) Vector logging uses hardcoded container name breaking the stated goal of multi-instance support. These must be fixed before deployment.
  • blueprints/supabase/template.toml requires immediate attention for syntax errors and configuration mismatches

Last reviewed commit: 6fd70d0

(5/5) You can turn off certain types of comments like style here!

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/721 **Author:** [@jdjimenez2312](https://github.com/jdjimenez2312) **Created:** 2/21/2026 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `Update-Supabase` --- ### 📝 Commits (7) - [`6fd70d0`](https://github.com/Dokploy/templates/commit/6fd70d06cb626ed471a4815bd290564583bb3f7d) Update Supabase 1.26.01 - [`eee9bb3`](https://github.com/Dokploy/templates/commit/eee9bb3d2e0e23d6a0d3c4fb3522e99e4c80f204) fix: correct syntax errors in template.toml for the logflare_public and logflare_private keys - [`5afdc7d`](https://github.com/Dokploy/templates/commit/5afdc7dcb26ab762deb09a0cb50b40b15cf697e5) fix: update comments for clarity in docker-compose.yml and template.toml - [`0390d5c`](https://github.com/Dokploy/templates/commit/0390d5c1239778b62f71bdcac75f0d806231d3cf) feat: add logflare_api_key variable and update env configuration - [`ffe08c0`](https://github.com/Dokploy/templates/commit/ffe08c028065f217128e31080e727032f5433cdc) fix: add missing comma in GOOGLE_PROJECT_NUMBER assignment in template.toml - [`238a017`](https://github.com/Dokploy/templates/commit/238a017d0fa33851743f2163805ff717f0e87f17) fix: update volume paths - [`55c4db2`](https://github.com/Dokploy/templates/commit/55c4db2b72db4215b0db593be8b604679ba49d50) fix: update realtime container name ### 📊 Changes **3 files changed** (+156 additions, -96 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/supabase/docker-compose.yml` (+58 -54) 📝 `blueprints/supabase/template.toml` (+97 -41) 📝 `meta.json` (+1 -1) </details> ### 📄 Description ## What is this PR about? New PR of Supabase is updated according to the original .yml and configured to allow multiple instances. ## 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. <!-- greptile_comment --> <h3>Greptile Summary</h3> Updates Supabase template from version 1.25.04 to 1.26.01 with multiple component version upgrades and configuration improvements. The PR includes changes to support multiple Supabase instances and aligns with the upstream Supabase docker-compose configuration. **Critical Issues Found:** - TOML syntax errors with missing closing quotes on lines 5-6 will prevent template parsing - Realtime service routing is broken - Kong URLs don't match the renamed container (lines 331, 351) - Vector logging configuration uses hardcoded container name instead of variable, breaking multi-instance support (line 844) **Notable Changes:** - Updated 10+ service versions (studio, auth, rest, realtime, storage, imgproxy, meta, functions, analytics, db, vector, supavisor) - Changed storage volume paths from `../files/volumes/storage` to `./volumes/storage` for consistency - Added new environment variables for storage S3 protocol configuration - Improved logging configuration with updated retry strategies - Added new volumes for snippets and edge functions management in studio service <h3>Confidence Score: 1/5</h3> - This PR has critical syntax and logic errors that will prevent Supabase from functioning - Multiple critical issues prevent this from working: (1) TOML syntax errors on lines 5-6 will cause template parsing to fail entirely, (2) Kong routing configuration has incorrect URLs that don't match the renamed realtime container, causing routing failures, (3) Vector logging uses hardcoded container name breaking the stated goal of multi-instance support. These must be fixed before deployment. - `blueprints/supabase/template.toml` requires immediate attention for syntax errors and configuration mismatches <sub>Last reviewed commit: 6fd70d0</sub> <!-- greptile_other_comments_section --> <sub>(5/5) You can turn off certain types of comments like style [here](https://app.greptile.com/review/github)!</sub> <!-- /greptile_comment --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-21 23:26:15 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No labels pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#7953