@matt Why not consider a Caddy-specific package manager that can be installed as a distro package? That way, you’d be able to leave the build process on the Caddy build servers but still automate, say, the creation of a Caddy user/service file/etc. Once we had a functional package manager/build environment, it could even be genericised for other go-based projects.
I think distro packages are a gigantic waste of time.
As someone who doesn’t particularly enjoy writing systemd service files, I think they’re a gigantic time-saver
Production users should use Docker.
I disagree. Firstly, docker doesn’t solve the issue we’ve run into (distributing a “package” with a user’s selection of plugins), and secondly I honestly don’t think Docker all that good. I don’t want to risk getting too off topic, mind, so I’ll shut up and we can have that conversation elsewhere if you fancy it.