Ok, this explains a lot and also clearly shows I never used this feature :)
I always assumed it would be the Caddy process itself taking care of downloading the update & replacing the binary, before restarting it.
I always assumed it would be the Caddy process itself taking care of downloading the update & replacing the binary, before restarting it.
To clarify: it doesn't, nor has it ever worked that way. You have to be the one to do that (or someone with privileges to write to that file on disk). Most production setups don't give Caddy that permission. And you have to trigger the upgrade too.