Great! I when I discovered it this morning, I thought, how could I have missed it, but I see now it hasn’t been out that long.
On that topic, what is the recommended way to upgrade? I now usually redownload a release file, try to remember which extensions I was using, and then copy it over the old one. Is there a better way? Is there a way to construct a URL that has all the necessary options?? Upgrades are almost once a month, so there must be a more automated way to take care of one’s infrastructure needs. How do other people do this?
That makes me wonder, what happens if a build release doesn’t have an extension that the site is using, does it just fail to run, or is it just that feature that won’t work?
Funny! Basically the answer is: use https://getcaddy.com
But which features can be specified is not clear. The source at getcaddy.com give the example of git,mailout. The full output of caddy -plugins is:
Is it only possible to specify the http.X features without the prefix?? But not all of them are listed on the webpage (nor do they work). And how about the DNS server type? And the DNS providers? Is there a full API for specifying on the command line what exactly one wants to get?
If line 3 is really needed for both new installs and upgrades, it should be incorporated in getcaddy.com’s script.
The 4th line, nowadays I get cp: cannot create regular file '/usr/local/bin/caddy': Text file busy if it’s still running. So in that case a reshuffle of lines 4 and 5 like:
That’s the download link. After choosing your configuration on the download page, right-click the download button for your platform and copy the link URL, that goes there.
No, when you replace the file you need to give it the capabilities to bind to low ports again.