I get that. The problem is, that requires me to know that the “latest” is 2.0.0
The docs specifically give out a curl and wget command. I believe the documentation is wrong and needs to be fixed.
No form of the curl or wget command can be used to download the latest.
Github allows the concept of downloading the latest tagged release but I think that works if you only have 1 asset file published. In this case, since multiple asset files are published, I think the documentation is wrong. The “using curl” and “using wget” portions must be removed
We’ll eventually have a build server which will make that easier, but for now we recommend either using a package repo (apt for debian/ubuntu, or Fedora COPR for fedora/centos) which will keep you updated, if you need auto-updates. Or you can do like you suggest and use the github API
Just so you know, “always downloading the latest” blindly (into production) is never a good idea.
Francis is right, we’ll probably eventually have a public API that lets you get version information. But this method of downloading Caddy (by using curl from GitHub releases) is just a command-line equivalent of using your browser to click the download link. It’s not intended for rolling installs on production systems. For that, use a proper package manager.