YuukanOO
SSL certificate handling
As far as I can see, there is no option to allow Traefik to generate it's SSL certificate automatically using f. e. a wildcard SSL cert using LetsEncrypt and the DNS API.
For now, seelf configures Traefik certificate resolvers with a TLS challenge.
This is the most straightforward way to get a valid certificate without messing too much with DNS configuration (requiring additional user manipulation).
But you're right and supporting DNS challenge could be a nice feature.
Do you think seelf could support something like Cloudflare argo tunnel? This is a nice feature of Coolify and would be cool to bring along here.
Additionally how could we go about using Cloudflare's DNS proxy here? This wouldn't completely work on the CF free tier as you can only issue certs to like x.example.com and not sub.x.example.com
Do you think seelf could support something like Cloudflare argo tunnel? This is a nice feature of Coolify and would be cool to bring along here.
It could be feasible but I don't know Cloudflare at all.
Additionally how could we go about using Cloudflare's DNS proxy here? This wouldn't completely work on the CF free tier as you can only issue certs to like x.example.com and not sub.x.example.com
Exposing services on paths instead of subdomains could probably be a solution to overcome this limitation. For example, the default service of an app named sandbox could take the subdomain sandbox.example.com and a second exposed service something like sandbox.example.com/_nameoftheotherservice.
Love that paths idea. Is that possible now? Apologies for the questions! Thank you for your time 😄