[Bug]: Listmonk compose file doesn't work when deploying from private repo

[ingokpp]

Description

There is a one-click setup for listmonk which works just fine, however, I need to start listmonk using a custom static directory to further customize it. I encountered an issue when trying to deploy listmonk using Coolify with a custom Docker Compose setup from a private repository.

Minimal Reproduction (if possible, example repository)

Steps to Reproduce

• Copy the docker-compose template into an empty repository.
• Create a new project in Coolify using the private repo -> Docker Compose option.
• Coolify recognizes all environment variables like $SERVICE_USER_POSTGRES and prefills them with some random values.
• Enter a service URL including the port 9000 at the end (e.g., https://listmonk.domain.com:9000/).
• Start the deployment.

Expected Behavior

Listmonk should be able to connect to the database and the deployment should succeed without any issues.

Actual Behavior

Listmonk is unable to connect to the database when deploying from a private repository using Docker Compose. However, when creating a project using the Docker Compose option and pasting the content of the file directly into the editor in the Coolify dashboard, everything works fine.

Exception or Error

No response

Version

v4.0.0-beta.306

[ingokpp]

Don't know if related but after deleting the project, the docker network still remains active. See Issue-2726

[ingokpp]

Closed because I know the problem is related to Issue-2729