both SUPBASE_URL and SUPABASE_PUBLIC_URL were set to the ENV ${SUPABASE_PUBLIC_URL}, which caused failure in the studio to access some supabase features (such as creating/reading buckets).
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_NUMBERHaven't checked.
Screenshots or Videos
🔄 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/618
**Author:** [@Aecron](https://github.com/Aecron)
**Created:** 12/21/2025
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `patch-1`
---
### 📝 Commits (1)
- [`c5903d0`](https://github.com/Dokploy/templates/commit/c5903d063d0fb4bbead3fc2cb71473d610c2b370) SUPABASE_URL in the Studio service fixed
### 📊 Changes
**1 file changed** (+2 additions, -2 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/supabase/docker-compose.yml` (+2 -2)
</details>
### 📄 Description
both SUPBASE_URL and SUPABASE_PUBLIC_URL were set to the ENV ${SUPABASE_PUBLIC_URL}, which caused failure in the studio to access some supabase features (such as creating/reading buckets).
This fix is in line with https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml
## What is this PR about?
Docker Compose SUPABASE_URL fixed to use the local docker kong instance instead of the public address.
## 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 no read, I just encountered the issue myself and bothered to publish the fix**
- [X] 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`~ **Haven't checked.**
## ~Screenshots or Videos~
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/618
Author: @Aecron
Created: 12/21/2025
Status: 🔄 Open
Base:
main← Head:patch-1📝 Commits (1)
c5903d0SUPABASE_URL in the Studio service fixed📊 Changes
1 file changed (+2 additions, -2 deletions)
View changed files
📝
blueprints/supabase/docker-compose.yml(+2 -2)📄 Description
both SUPBASE_URL and SUPABASE_PUBLIC_URL were set to the ENV ${SUPABASE_PUBLIC_URL}, which caused failure in the studio to access some supabase features (such as creating/reading buckets).
This fix is in line with https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml
What is this PR about?
Docker Compose SUPABASE_URL fixed to use the local docker kong instance instead of the public address.
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-templateI have no read, I just encountered the issue myself and bothered to publish the fixI 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:Haven't checked.closes #ISSUE_NUMBERScreenshots or Videos🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.