IP-based access restriction for Coolify Dashboard

[Talkless]

Currently Dashboard is accessible via https://coolify.example.com and via http://coolify.example.com:8000.

:8000 can be protected via firewall, but it's not TLS...
:8000 can be protected via firewall, but Dashboard is still available via main domain coolify.example.com, so it's moot.

So there is no solution to protect Coolify from "outsideers". There is no even "incorrect login" log to enable Fail2Bar/sshguard, etc...

Could we have Dasbhoard confguration to utilize ipAllowList Traefic middleware, as discussed in #10303 (comment) ?

Or maybe allow to configure Dashboard to be accessible ONLY via custom port, but ALSO with TLS enabled?

[sebastien3k]

I opened a related proposal for a more general Caddy extension point that would also cover this use case while supporting exceptions such as a public deploy webhook endpoint: #11236