Thanks for the feedback! Glad you have had a good experience with it.

That blog post is pretty old. We do have a current upgrade guide here in our docs: https://caddyserver.com/docs/v2-upgrade

We also have a (sort of deprecated) wiki with some (slightly outdated) high-level improvements listed: https://github.com/caddyserver/caddy/wiki/v2:-Improvements

Another piece of feedback: It’s scary to consider using such a crucial piece of software in production when documentation is referred to as “sort of deprecated” and “slightly outdated.”

Because that's the old documentation, from early betas of Caddy v2.

The official documentation at https://caddyserver.com/docs/ is up to date, and not deprecated.

Oh! That’s good news. I’m excited to give it a try either way.

Adoption for me would be to have an official apt repo :)

I mean, we want one too, but it's ridiculously hard: https://news.ycombinator.com/item?id=23072385

Help? :D

I think the parent poster would already be happy with an APT repo provided by Caddy. It wouldn’t need to be included in Debian itself.

When you can make dpkg files, making an apt repo is trivial (using reprepro shipped with Debian)

And when it’s your repo, you make the rules about packaging what dependencies into which file(s)

But by having an apt repo (that users would subscribe to), you make it much easier for users to keep up to date

We do have one!

https://caddyserver.com/docs/install#debian-ubuntu-raspbian

Oooh this is great news, I can finally quit updating Caddy by hand!

Talk about a bummer... Golang makes it easy to make static binaries. Way too easy for the distro apparently.

Deb files will be just fine.

Pretty close to official. https://caddyserver.com/docs/install