github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-05-07 09:10:20 -05:00
Code Issues 1.2k Packages Projects Releases Wiki Activity

[PR #814] feat: updated supabase versions and required config #2925

New Issue
Open
opened 2026-04-23 03:38:39 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-23 03:38:39 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/814
Author: @mattias-wiberg
Created: 4/20/2026
Status: 🔄 Open

Base: canary ← Head: feat/update-supabase-versions

📝 Commits (1)

  • a0883dc feat: updated supabase versions and required config

📊 Changes

2 files changed (+864 additions, -192 deletions)

View changed files

📝 blueprints/supabase/docker-compose.yml (+210 -93)
📝 blueprints/supabase/template.toml (+654 -99)

📄 Description

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:

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)

    P2 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)

🔄 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/814 **Author:** [@mattias-wiberg](https://github.com/mattias-wiberg) **Created:** 4/20/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `feat/update-supabase-versions` --- ### 📝 Commits (1) - [`a0883dc`](https://github.com/Dokploy/templates/commit/a0883dc5ee2a8d2a044d85a6d77d7891507c09f1) feat: updated supabase versions and required config ### 📊 Changes **2 files changed** (+864 additions, -192 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/supabase/docker-compose.yml` (+210 -93) 📝 `blueprints/supabase/template.toml` (+654 -99) </details> ### 📄 Description 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: - [x] 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 - [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong. - [x] 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_comment --> <h3>Greptile Summary</h3> 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. <h3>Confidence Score: 5/5</h3> 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) <!-- greptile_failed_comments --> <details><summary><h3>Comments Outside Diff (1)</h3></summary> 1. `blueprints/supabase/template.toml`, line 1 ([link](https://github.com/dokploy/templates/blob/d30b89e08243ff39f9c7ecec73fbd38631581e43/blueprints/supabase/template.toml#L1)) <a href="#"><img alt="P2" src="https://greptile-static-assets.s3.amazonaws.com/badges/p2.svg?v=7" align="top"></a> **`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](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2)) </details> <!-- /greptile_failed_comments --> <sub>Reviews (1): Last reviewed commit: ["feat: updated supabase versions and requ..."](https://github.com/dokploy/templates/commit/d30b89e08243ff39f9c7ecec73fbd38631581e43) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=29047289)</sub> > Greptile also left **1 inline comment** on this PR. **Context used:** - Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2)) <!-- /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-04-23 03:38:39 -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 Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#2925
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?