Caddy 0.10 Released
caddyserver.com
Caddy 0.10 Released
1–10 of 128 posts
Re: Caddy 0.10 Released
#2Re: Caddy 0.10 Released
#3When would I use Caddy, rather than using nginx and configuring Let's Encrypt for myself? Honest question.
Re: Caddy 0.10 Released
#4When would I use Caddy, rather than using nginx and configuring Let's Encrypt for myself? Honest question.
Re: Caddy 0.10 Released
#5When would I use Caddy, rather than using nginx and configuring Let's Encrypt for myself? Honest question.
But seriously, for all "hobby" projects I've started recently, and even some production services now, I go straight to caddy.
My config consists of a 1 line global config file:
import sites-enabled/*
And 90% of the individual services have this config: example.com {
proxy / http://localhost:5000 {
header_upstream Host {host}
}
}
Compared to nginx it's just so much simpler and so far I haven't found myself missing a single feature. (In fact, caddy has active health checks, which nginx only supports for its extortionate enterprise fee)Re: Caddy 0.10 Released
#6When would I use Caddy, rather than using nginx and configuring Let's Encrypt for myself? Honest question.
I feel like the niche Caddy's trying to fill is for people who don't want to bother with that, or don't want to learn. If you already know how to set up nginx and LE (like you and I do), its only appeal is relatively minor: potentially saving a quarter or half hour.
Re: Caddy 0.10 Released
#7When would I use Caddy, rather than using nginx and configuring Let's Encrypt for myself? Honest question.
Why would I use nginx and go through the hassle of configuring let's encrypt and sane SSL settings when I could just use caddy? But seriously, for all "hobby" projects I've started recently, and even some production services now, I go straight to caddy. My config consists of a 1 line global config file: import sites-enabled/* And 90% of the individual services have this config: example.com { proxy / http://localhost:…
Re: Caddy 0.10 Released
#8To me, HPKP with preloading seems like a more reliable approach (and browsers shouldn't allow this to be overridden [1]).
[1] If this breaks corporate MitM attacks, great. This practice always struck me as incredibly invasive and I'd personally be concerned if an employer was doing this. I think some traffic data should be able to be logged and timestamped in case of abuse (e.g. SNI info, TCP connections, DNS lookups) but I don't see a need to intercept application data - and honestly, it seems like the vast majority of these appliances hinder security.
Re: Caddy 0.10 Released
#9When would I use Caddy, rather than using nginx and configuring Let's Encrypt for myself? Honest question.
I made the complete switch to Caddy just because the configuration is simplified and it has features like git webhooks built-in. Setting up BasicAuth on a directory is one line in the config. And it's fast. No issues so far, been using Caddy for over a year now.
Re: Caddy 0.10 Released
#10Earlier quoted context omitted.
I feel like the niche Caddy's trying to fill is for people who don't want to bother with that, or don't want to learn. If you already know how to set up nginx and LE (like you and I do), its only appeal is relatively minor: potentially saving a quarter or half hour.
I think over time there will be a similar server written in Rust, where at least we can be sure that there are no buffer overflows..until then nginx is probably better in every situation.