Hacker News Reader

Comment by k_bx | Hacker News Reader

Just curious. I use Ubuntu on my servers (as many do) and I deploy everything as standard Systemd service (even my apps). However, when I wanted to try out Caddy, I realized they don't provide you with one, so you have to write your own scripts putting systemd config files, enabling the service etc. Is this what everyone does these days? Seemed kinda strange for mainstream software.

View on HN

That's really more of a packaged/non-packaged thing, though, isn't it? Like, I once installed caddy on a CentOS (RIP) system by running `yum install caddy` and that did give me the right systemd config out of the box, which I wouldn't expect to get from a out-of-tree binary I just plopped on the system.

But they do provide systemd unit files:

https://caddyserver.com/docs/running#unit-files

Or are you saying they should be included with the download?

It's just so strange. They provide two systemd files, you need to choose one, edit (!) it, put on the machine etc. Comparing with nginx's boring apt-get install that does the right thing this feels like non-mature way to distribute things. Especially for people who script and document all of their server setup procedures.

Take a look at the Debian/Ubuntu install instructions. “Installing this package automatically starts and runs Caddy as a systemd service” https://caddyserver.com/docs/install#debian-ubuntu-raspbian

All right, totally missed it then, thank you

Reply on news.ycombinator.com