-
Notifications
You must be signed in to change notification settings - Fork 267
Description
Template Name
Supabase
Relevant Logs of the Error
Creating multiple instances of Supabase on the same machine will give this error:
Steps to Reproduce the Error
- Deploy the Supabase template - this will be project one
- Deploy the same template in a new project - this is project two and doesn't work without changing the ports
Environment Information
Operating system: Debian 12
Dokploy version: v0.25.11
VPS provider: OVH
Template version: latestWhen does this error occur?
During template deployment
Additional Context
The workaround im using is changing these variables in my ENV:
POSTGRES_PORT=5432 -> POSTGRES_PORT=5532
POOLER_PROXY_PORT_TRANSACTION=6543 -> POOLER_PROXY_PORT_TRANSACTION=6643
It should 100% be possible to route different domains for example data.project-one.com -> instance 1 and data.project-two.com to the different instances and make supabase not accessable by the machine IP at all, I just can't seem to figure it out.
I've tried creating a new entry point for postgres in the traefik.yml, then using labels to route request based on the domain to their coressponding instance however this just didn't work - no error messages just no success.
Any help would be much appreciated!
Will you send a PR to fix it?
Maybe, need help