[Bug]: Supabase db expose port

[apertureless]

Description

I have deployed the supabase application, mostly with default settings. In order to push db migrations from the location supabase instance, I need to specify the --db-url

supabase db push --db-url="postgres://postgre[...]

In order for this to work, I have to expose the db port in coolify.

In the DB container I have set a public port and checked the checkbox "Make it publicly available". But the port is not exposed. Also if I set a name for the container, it keeps the old

Minimal Reproduction (if possible, example repository)

1. Create supabase application
2. Go to Settings in DB container
3. Set public port
4. "Set Make it publicly available"

Exception or Error

Port not exposed

Version

v4.0.0-beta.265

[Markus-Ende]

Just found, that even if I create the destination via Servers -> other server -> Destinations, they always get created on localhost

[Geczy]

you can update the service compose yaml to expose the port

[boyhax]

you can update the service compose yaml to expose the port

i have same issue . i tried to add ports in compose file but the coolify version dont have it .so the coolify parsing of the file is ignoring ports by default.

no other solutions?

[Geczy]

make a new project and copy the docker compose yaml for supabase and add the ports

[zilahir]

you can update the service compose yaml to expose the port

i have same issue . i tried to add ports in compose file but the coolify version dont have it .so the coolify parsing of the file is ignoring ports by default.

no other solutions?

i've managed to get it work that way:

    ports:
      - '5432:5432'

on the supabase-db service.

[apertureless]

you can update the service compose yaml to expose the port

Yeah, but I would assume the UI checkbox would do the same.

[CarefulGuru]

Having the same issue with the MongoDB service - checking the "publicly available" box doesn't open it on the specified port

[Ryan-andpro-digital]

I think once you select 'Make it publicly available' it creates an nginx docker container that does the forwarding (@andrasbacsai correct me if I'm wrong :) ) - however, mine is stuck in a restarting loop (may or may not be the same sort of issue).

Before enabling

After enabling

logs error:

2024/06/07 11:01:58 [emerg] 1#1: invalid port in upstream "m0s8w4s:" in /etc/nginx/nginx.conf:12
nginx: [emerg] invalid port in upstream "m0s8w4s:" in /etc/nginx/nginx.conf:12

[yaberkane05]

having the same problem here.

you can update the service compose yaml to expose the port

Yeah, but I would assume the UI checkbox would do the same.

I unchecked the make public box to avoid port conflict, then did this. it worked !