News for hackers. Stuff that matters.
Re:HTTP/2 is not the future, it’s the present by sametmax on Wednesday April 12, 2017 @08:10AM (#14096831)
But this implies you can then deploy your caddy server. Which means a private server with root rights. Do you realize most devs don't even know server admin ? If you know the command line, you are not most dev. You are far, far away from the reality of enterprise software.

Tomcat and apache are still massively deployed. If you moved to nginx years ago, remember than it's still a new toy for a huge number of people. So caddy...

Re:HTTP/2 is not the future, it’s the present by jonathanoliver on Thursday April 13, 2017 @12:08AM (#14104096)
Caddy doesn't require root. You can easily use systemd/upstart/custom scripts to run as an unprivileged user.
Re:HTTP/2 is not the future, it’s the present by vetinari on Wednesday April 12, 2017 @11:01AM (#14098298)
Apache is easy to configure with TLS or Let's Encrypt.

The only unfortunate thing is, that RHEL7/CentOS7 have OpenSSL 1.0.1 and mod_http2 requires OpenSSL 1.0.2. Thus no http2 there.

Re:HTTP/2 is not the future, it’s the present by openasocket on Wednesday April 12, 2017 @10:09AM (#14097819)
You don't need caddy, you just need a self-signed cert, which is pretty easy to generate.