Lack of Clear Documentation for Running Supabase #31

New Issue

GiteaMirror · 2025-11-22T20:29:30-06:00

GiteaMirror commented

2025-11-22 20:29:30 -06:00

Originally created by @e-Naeim on GitHub (Apr 17, 2025).

Thanks for providing a Supabase template for Dokploy.. I really appreciate the effort to simplify deployments.

However, I ran into several issues due to the lack of clear documentation. I followed these steps:
1. Went to Dokploy and selected the Supabase template.
2. Clicked “Deploy” without modifying anything.
3. Deployment was successful, but there’s no guidance on:
• How to access Supabase Studio.
• How to properly configure domains or subdomains for the Studio.
• How to retrieve the Database URL.
• How to access Supabase backend endpoints for Auth and other services.

For example, I tried adding a new domain for the Studio in the dashboard and redeployed, but it still doesn’t work — it gives me "refused to connect".. not sure if that’s an issue on my side or a configuration step I missed.

It would be great to have:
• A step-by-step post-deployment guide.
• Clear instructions on setting up the Studio access.
• Information on environment variables (like SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_DB_URL, etc.).

Let me know if there’s something I’m overlooking.

Thanks again!

Originally created by @e-Naeim on GitHub (Apr 17, 2025). Thanks for providing a Supabase template for Dokploy.. I really appreciate the effort to simplify deployments. However, I ran into several issues due to the lack of clear documentation. I followed these steps: 1. Went to Dokploy and selected the Supabase template. 2. Clicked “Deploy” without modifying anything. 3. Deployment was successful, but there’s no guidance on: • How to access Supabase Studio. • How to properly configure domains or subdomains for the Studio. • How to retrieve the Database URL. • How to access Supabase backend endpoints for Auth and other services. For example, I tried adding a new domain for the Studio in the dashboard and redeployed, but it still doesn’t work — it gives me "refused to connect".. not sure if that’s an issue on my side or a configuration step I missed. It would be great to have: • A step-by-step post-deployment guide. • Clear instructions on setting up the Studio access. • Information on environment variables (like SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_DB_URL, etc.). Let me know if there’s something I’m overlooking. Thanks again!

GiteaMirror commented

2025-11-22 20:29:30 -06:00

@malko commented on GitHub (Apr 21, 2025):

Hi @e-Naeim,

You should not add a domain for the studio service. Normally a domain should have been created for kong service which is the only one you need for the current supabase template available (version 1.24.07).

for env vars you should at least setup:

SUPABASE_HOST=your-configured-domain.com
JWT_SECRET=seebelow
ANON_KEY=seebelow
SERVICE_ROLE_KEY=seebelow
DASHBORD_PASSWORD=thisIsThePasswordForStudio
SITE_URL=http://url-of-your-frontend-app-that-use-supabase

in the docker-compose.yml you probably want to change the line

SUPABASE_URL: http://kong:8000
# to 
SUPABASE_URL: http://${SUPABASE_HOST} # or https depends on your setup

You should have a look at this page: https://supabase.com/docs/guides/self-hosting/docker for guidance to create you own JWT_SECRET, ANON_KEY, and SERVICE_ROLE_KEY (in a future version of template you will probably have them automatically generated).

A newer version of the template is pending PR approval, the changes in docker-compose will not be necessary anymore

In a more general way when you're loading a template there's most of the time links to the related documentation. For now Dokploy templates doesn't have more documentation than that, or some comments inside the docker-compose file or the env file.

Hope this helps

@malko commented on GitHub (Apr 21, 2025): Hi @e-Naeim, You should not add a domain for the studio service. Normally a domain should have been created for kong service which is the only one you need for the current supabase template available (version 1.24.07). - for env vars you should at least setup: ``` SUPABASE_HOST=your-configured-domain.com JWT_SECRET=seebelow ANON_KEY=seebelow SERVICE_ROLE_KEY=seebelow DASHBORD_PASSWORD=thisIsThePasswordForStudio SITE_URL=http://url-of-your-frontend-app-that-use-supabase ``` - in the docker-compose.yml you probably want to change the line ``` SUPABASE_URL: http://kong:8000 # to SUPABASE_URL: http://${SUPABASE_HOST} # or https depends on your setup ``` You should have a look at this page: https://supabase.com/docs/guides/self-hosting/docker for guidance to create you own JWT_SECRET, ANON_KEY, and SERVICE_ROLE_KEY (in a future version of template you will probably have them automatically generated). A newer version of the template is pending PR approval, the changes in docker-compose will not be necessary anymore In a more general way when you're loading a template there's most of the time links to the related documentation. For now Dokploy templates doesn't have more documentation than that, or some comments inside the docker-compose file or the env file. Hope this helps

GiteaMirror commented

2025-11-22 20:29:30 -06:00

@fael-atom commented on GitHub (May 9, 2025):

@malko thank you very much! Your explanation solved my situation. You just need to access the link below and paste the JWT_TOKEN already present in the environment so that it can be possible to generate new ANON_KEY and SERVICE_ROLE_KEY.

https://supabase.com/docs/guides/self-hosting/docker#generate-api-keys

@fael-atom commented on GitHub (May 9, 2025): @malko thank you very much! Your explanation solved my situation. You just need to access the link below and paste the JWT_TOKEN already present in the environment so that it can be possible to generate new ANON_KEY and SERVICE_ROLE_KEY. https://supabase.com/docs/guides/self-hosting/docker#generate-api-keys

GiteaMirror commented

2025-11-22 20:29:31 -06:00

@samiralavi commented on GitHub (Nov 15, 2025):

The supabase template is updated to the recent release in https://github.com/Dokploy/templates/pull/537.

@samiralavi commented on GitHub (Nov 15, 2025): The supabase template is updated to the recent release in https://github.com/Dokploy/templates/pull/537.

GiteaMirror referenced this issue

2025-11-22 20:31:55 -06:00

[PR #31] [MERGED] chore: bump kimai version to 2.31.0 #178

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#31