Hacker News Reader

Comment by regecks | Hacker News Reader

When I went to use Caddy (because I love the idea of it), I was disappointed to find that there was no yum repo.

Of course, this makes sense because you have to compile the features in.

But, it would still be nice to have deployment automate-able. Maybe an Ansible role that combines the feature list you need and downloads it via an API.

It's the major, and only reason I quit and went back to nginx.

View on HN

This is/was also pretty much my concern, and there is a whole thread about this on their forum here: https://forum.caddyserver.com/t/packaging-caddy/61

The repo does contain some init/service scripts for using Caddy on various Linux and BSD distributions. They are created and maintained by the community, but this combined with the binary should make it quite easy to package: https://github.com/mholt/caddy/tree/master/dist/init

Also, it seems somebody already started working on A Ubuntu 14.04 Caddy Repository: https://github.com/alexandreteles/caddy-repo

Why not create your own package? Can do a basic one with fpm

Because then you also need to host a feed, and keep it updated when new releases become available, and keep it updated when new plugin releases become available, and ensure the feed stays up, and maintain patches, and maintain required dependencies. All the things that package maintainers (thank you!) do for the ecosystem. Unless there's substantial gain why not just stick with Nginx?

For what it's worth though FPM is awesome, and has made my life better a number of times. If you have to have software that isn't packaged and you aren't familiar with packaging, look into FPM.

https://github.com/jordansissel/fpm

What dependencies? This is statically compiled go.

Binaries are available, automating a download and wrapping into a package with FPM is not that much effort.

Right, it's not a tonne of work if you need it or really want it. But it's still extra effort to move away from a supported package provided by the package management software. Not providing repos means you lose the users who might want to play around with it but don't have any packaging experience. This shouldn't be very controversial.

Reply on news.ycombinator.com