Package Details: caddy-full-bin 0.11.1-1

Git Clone URL: https://aur.archlinux.org/caddy-full-bin.git (read-only)
Package Base: caddy-full-bin
Description: A configurable, general-purpose HTTP/2 web server for any platform (All features enabled)
Upstream URL: https://caddyserver.com
Keywords: http2 proxy webserver
Licenses: Apache
Conflicts: caddy, caddy-all-features, caddy-git
Provides: caddy
Submitter: klingt.net
Maintainer: klingt.net
Last Packager: klingt.net
Votes: 24
Popularity: 0.000542
First Submitted: 2016-07-27 09:09
Last Updated: 2018-11-19 10:33

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

mqs commented on 2016-09-29 15:32

@klingt.net Thanks for your advice last time!

If you change the path to /usr/bin/caddy, you should patch/change that in the service-file too. Currently it's not starting the service with the error-msg

caddy.service: Failed at step EXEC spawning /usr/local/bin/caddy: No such file or directory

klingt.net commented on 2016-09-29 14:00

@fanningert Thanks for the tip regarding `makedepends`. If you have an idea for the script please open a PR in github.

fanningert commented on 2016-09-29 13:55

@klingt.net
You should move the 'patch' depend into the makedepends, because it is only needed for creation of the package.

Yes you are right, there should be a migration process for user who is installed the package with the default caddy user and group. I think the simplest way is a simple script in the package and a notification on the install process step for the user.

klingt.net commented on 2016-09-29 12:38

If the service patch in `caddy-full-bin-0.9.3-4` fails then `rm -rf ~/.cache/pacaur/caddy-full-bin` should fix it.

klingt.net commented on 2016-09-29 12:32

@fanningert I just finished my patch for the service file and binary directory.
I would also write a patch for the user and group if it won't break existing installations. I am not a 100% about the implications of such a change.

Take for example if someone is running caddy as `www-data` and a new package release would change the user to `http` then the server maybe loses permission to read the webroot etc.
I think I must inform caddy users somehow (maybe by printing a warning in the PKGBUILD) before changing the default user.

fanningert commented on 2016-09-29 12:13

@klingt.net
I created a modified version of your PKGBUILD.
https://github.com/fanningert/PKGBUILDs/tree/master/aur/caddy-http-full

* User and group of service is changed to 'http' and 'http'
* Modified service file for Arch Linux systemd release
* Changed the directory for the binary to /usr/bin

vith commented on 2016-09-29 12:04

@klingt.net yeah

klingt.net commented on 2016-09-29 11:59

@vith what is the correct path for the binary, /usr/bin/caddy?

vith commented on 2016-09-29 11:00

@klingt.net

The README here https://github.com/mholt/caddy/tree/master/dist/init says they only the service definition to be an unsupported example; the user/group should be changed to the appropriate default for Arch.

Also the binary should not be installed to /usr/local/bin

fanningert commented on 2016-09-29 10:32

@klingt.net
with the base install I get follwoing error

2016/09/29 12:29:47 listen tcp :443: bind: permission denied

The problem is that the service file is updated with some changes for newer systemd instances, but three lines are commented. The are important for ArchLinux systemd released version (231 today)

;CapabilityBoundingSet=CAP_NET_BIND_SERVICE
;AmbientCapabilities=CAP_NET_BIND_SERVICE
;NoNewPrivileges=true

After uncomment this lines caddy is working again.