SUPABASE_URL in the Studio service fixed #618
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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