Caddy – The HTTP/2 Web Server with Automatic HTTPS

Re:Caddy – The HTTP/2 Web Server with Automatic HTTPS by shubhamjain on Wednesday April 25, 2018 @06:34AM (#16920231)

I didn't notice that you can compile the source code yourself to avoid paying for the license. That seems to be a nice alternative.

[ Parent | on HN ]

Re:Caddy – The HTTP/2 Web Server with Automatic HTTPS by mfontani on Wednesday April 25, 2018 @07:23AM (#16920485)

Only if you're not using it for commercial stuff. If you're using it for commercial stuff you have to pay the $25/month

[ Parent | on HN ]

Re:Caddy – The HTTP/2 Web Server with Automatic HTTPS by pfg on Wednesday April 25, 2018 @07:40AM (#16920577)

The code is released under the Apache License. You're free to compile the source code and use it commercially. You're not allowed to do that with the official binaries.

[ Parent | on HN ]

Re:Caddy – The HTTP/2 Web Server with Automatic HTTPS by wccrawford on Wednesday April 25, 2018 @08:00AM (#16920690)

My understanding of their license page is different.

"If your company uses official Caddy binaries internally, in production, or distributes Caddy, a commercial license is required."

"If I build Caddy from source, which license applies?" "The source code is Apache 2.0 licensed."

https://caddyserver.com/products/licenses

[ Parent | on HN ]

Re:Caddy – The HTTP/2 Web Server with Automatic HTTPS by jstanley on Thursday April 26, 2018 @06:31AM (#16930606)

Would be interested to see how reproducible builds would interact in such a situation.

I.e. you get a byte-identical binary file if you build it yourself, but you don't have to pay the $25/mo. Even though you end up at exactly the same place.

Something like http://ansuz.sooke.bc.ca/entry/23 "What colour are your bits?" I suppose.

[ Parent | on HN ]