Package Details: caddy 0.11.0-1

Git Clone URL: (read-only)
Package Base: caddy
Description: HTTP/2 Web Server with Automatic HTTPS
Upstream URL:
Licenses: Apache
Submitter: crvv
Maintainer: crvv
Last Packager: crvv
Votes: 28
Popularity: 0.828279
First Submitted: 2016-09-22 04:09
Last Updated: 2018-05-11 03:58

Latest Comments

1 2 3 Next › Last »

hendry commented on 2018-09-08 13:26

UPDATE: Sorry for the noise, a reboot sorted it out.

On my rpi, my caddy has stopped working. I see:

Sep 08 21:22:46 study systemd[4122]: caddy.service: Failed to determine user credentials: No such process Sep 08 21:22:46 study systemd[4122]: caddy.service: Failed at step USER spawning /usr/bin/caddy: No such process

In the logs. Ummm, /usr/bin/caddy is there so I am very confused.

Main process exited, code=exited, status=217/USER

axionl commented on 2018-05-25 00:59

@crvv Yep. So, I hope you can give this default environment variable on PKGBUILD. Because I wanna add this package to archlinuxcn repository and when you building the package on the container (extra-x86_64-build from devtools) , the namcap checking will return an error and the package cannot be published.

crvv commented on 2018-05-24 05:47

@axionl Do you try to run makepkg on a machine without libc? I think this is impossible because pacman depends on glibc. If you want a binary which doesn't depend on libc, you can add export CGO_ENABLED=0 in PKGBUILD. And this is the default when you do cross compiling. glibc donsn't appear in dependencies of other packages (like

axionl commented on 2018-05-23 14:15

missing a 'glibc' as depend?

ReDemoNBR commented on 2018-04-25 03:25

Builds and works nicely in my Raspberry Pi Zero W, which is arch armv6h.

I think it is safe to add it to the list of archs :)

crvv commented on 2018-03-05 14:16

@carlwgeorge Done.

carlwgeorge commented on 2018-03-05 13:43

@crvv Can you remove me as a co-maintainer?

crvv commented on 2017-11-24 07:14

"/var/log/caddy" was added in ReadWritePaths.

Svenstaro commented on 2017-11-22 10:56

I think /var/log/http or /var/log/caddy should be the expected location for logs as a similar system is also used by apache and nginx. I don't think there's a bad security implication waiting there.

crvv commented on 2017-11-22 10:03

On my server, I just wrote 'log stderr' in Caddyfile and read access log with `journalctl -fu caddy`.
I am not sure whether it's a good decision to add a ReadWriteDirectories for everyone.
Custom systemd directives can be added with `systemctl edit caddy.service`.