MaxGhostB
You’re meant to read https://caddyserver.com/docs/caddyfile/concepts#structure first, which explains that directives always go within a site block, and can sometimes be nested within other special directives like handle and route.
I understand what they meant, but it’s broad/vague, and not specific/actionable.
We do have a tutorials section in the docs, and we have the https://caddyserver.com/docs/caddyfile/patterns page which are that.
Our question is how are those lacking? Just saying “more please” doesn’t help because we don’t know what the need is. We can’t imagine every single possible usecase, because it’s actually infinite. Caddy is a “general purpose webserver” which means “it can do just about anything”.
Help us by telling us what specifically what usecase is important to you. We don’t have telemetry, we need users to tell us.
Thanks, that’s helpful. Yeah the docs for auto_https should explain up-front that this only affects the feature called “Automatic HTTPS” and does not change the default port/procotol of Caddy, which is always HTTPS unless otherwise specified (i.e. by using http:// as a site address prefix, or :80 as a suffix).
😬 Well, that’s not helpful. Without specific feedback, there’s nothing we can do to improve the docs. It’s exhausting to read vague complaints about the docs, because it’s 90% of the feedback we get.
But yes, please do reach out (open a GitHub issue, comment on the forums etc) if you do notice something that doesn’t meet your expectations in the docs.