Hey Francis, let me go back to the project. I managed to stitch together our use case by reading - https://caddy.community/t/https-for-dynamic-subdomains-and-c

Hey Francis, let me go back to the project. I managed to stitch together our use case by reading - https://caddy.community/t/https-for-dynamic-subdomains-and-custom-domains/7921/4 https://caddy.community/t/https-for-dynamic-subdomains-and-c... - https://caddy.community/t/best-practise-for-multiple-tenant-multiple-https-domain-server/2082 https://caddy.community/t/best-practise-for-multiple-tenant-... and various GitHub issues Our use case was: "serve SSL certificates on the fly for users hitting :443 AND users hitting *.checklyhq.com, then proxy some content." The documentation looks visually nice, but is hard to parse as the layout of the config file (and the hierarchy of the items in it) is separate from the explanation of what they do. I was continuously doing a Ctr+F to find words on the page. Example: https://caddyserver.com/docs/caddyfile/options https://caddyserver.com/docs/caddyfile/options Here the stanzas are clickable. https://caddyserver.com/docs/caddyfile/directives/tls https://caddyserver.com/docs/caddyfile/directives/tls Here not. Last thing. The docs present a lot of config examples in snippets, but seeing how to use them in a full, syntactically correct file was hard. I felt I was missing the big picture. Sorry to not be more concrete, it was some time ago.