feat: Custom Traefik entrypoint support

[arnokristiaan]

We have a case in which we want to define a custom Traefik entrypoint in the proxy labels, for security purposes, but we cannot really use the entrypoint in the applications. This is caused because variables cannot be used in labels in order to specify a host. This PR mitigates that problem by using the Coolify domain settings for an application.

Usage

In the settings of an application under General > Domains you can set a domain like https://your.own.domain:8888 which will tell the proxy to route traffic to https://your.own.domain to the container on internal port 8888.

To use the custom entrypoint, which you created through your custom proxy labels, you change the domain to https://[email protected]:8888. This will do the same but will use the "your-custom-entrypoint" as entrypoint instead of the default https or http entrypoints.

Multiple entrypoints are supported by comma-separation.

Changes

• Refactored bootstrap/docker.php to get rid of some duplicate code
• Started using the user info to be able to tell coolify which Traefik entrypoint it should use in the labels, it defaults back to http and https

[arnokristiaan]

@andrasbacsai Would it be possible to receive any comment on why this PR is closed?

[andrasbacsai]

It was a mistake, sorry. I recreated the next branch and it auto-closed this PR.

[arnokristiaan]

@andrasbacsai That explains it, thanks for the response!

[Windol]

How will this implementation work? How can I make use of it?

[arnokristiaan]

@Windol I've edited the description of this PR with a usage chapter to explain how to use it.