Caddy – The HTTP/2 Web Server with Automatic HTTPS
caddyserver.com
Caddy – The HTTP/2 Web Server with Automatic HTTPS
1–10 of 66 posts
Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS
#2Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS
#3As someone who is very very new to hosting their own services, this was an absolute piece of cake to set up. My first time dealing with reverse proxies and it took less than an hour to get going.
Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS
#4Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS
#5> Caddy obtains certificates for you automatically using Let's Encrypt.
Not sure why that is not stated front and centre. It's a good idea.
Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS
#6Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS
#7Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS
#8What's interesting is that it's the first web server not focused on speed or performance but on the user experience. I love nginx, but I had huge headaches configuring it when migrating php apps with huge htaccess rules to nginx. The terms of the license do not seem super clear though.
I also had this issue whenever I did migrations between different web applications that used different URL structures. To preserve my sanity, I now do the redirects in the application level.
I predict nginx will get a lot of competition from servers and applications written in Rust. Until then, it's viable as a reverse proxy and serves static files really great.
Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS
#9What's interesting is that it's the first web server not focused on speed or performance but on the user experience. I love nginx, but I had huge headaches configuring it when migrating php apps with huge htaccess rules to nginx. The terms of the license do not seem super clear though.
Caddy looks promising and simpler. Might have to take a look this weekend.
Re: Caddy – The HTTP/2 Web Server with Automatic HTTPS
#10What's interesting is that it's the first web server not focused on speed or performance but on the user experience. I love nginx, but I had huge headaches configuring it when migrating php apps with huge htaccess rules to nginx. The terms of the license do not seem super clear though.
> I had huge headaches configuring it when migrating php apps with huge htaccess rules to nginx I also had this issue whenever I did migrations between different web applications that used different URL structures. To preserve my sanity, I now do the redirects in the application level. I predict nginx will get a lot of competition from servers and applications written in Rust. Until then, it's viable as a reverse pr…
I'm open to competition in the field, I'm not sure the competition will emerge as fast as people think (just like competition for other well-established software bricks in general).