All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Caddy v2 released
Quite surprised no thread about it yet, anyway just copy pasting:
Caddy 2 is a highly extensible, self-hosted platform on which you can build, configure, and deploy long-running services ("apps").
Caddy ships with apps for an HTTPS server (static files, reverse proxing, load balancing, etc.), TLS certificate manager, and fully-managed internal PKI. Caddy apps collaborate to make complex infrastructure just work with fewer moving parts.
For example, the config shown here keeps your TLS certificates renewed for other programs to use; no external tools or HTTP daemon required!
Providing a unified configuration, on-line config API, and automatic documentation for all apps, Caddy is nearly infinitely extensible. Thanks to its unique modular architecture, we can offer unlimited features without bloating the code base.
Comments
Finally, amazing server I've been using for reverse proxy and to serve html files
Now they need to improve and fix the docs, due to a lot of changes during the development
Never tried it, how does it compares (performance) to Apache, Nginx and Hitch?
I'd say Hitch > Nginx and Apache & Caddy are both less efficients for quick TLS termination and efficiency at high load but I could be wrong as I never tried Caddy.
I don't know about performance. I used it for my self. But with one line I can create a reverse proxy with https and I have to do nothing
Oh, last time I've tried they were asking for some money to install on servers?
"We're open source but hey fuck you we need money", so this kind of BS never should be named open source.
Nginx can actually be quite slow - I've got a few sites running ASP.NET Core and sticking Nginx in front of them actually reduces the max requests per second quite a bit. Having said that, I haven't tried Caddy yet myself, so I'm not sure how it compares.
Caddy is totally open source. Just download the binary an run as service. Maybe they offer a paid solution, but not mandatory
Actually official binaries were a paid solution. It was free only for personal projects.
Seems to be pretty decent. I've found on internet a bench result made with h2load test tool and results are good.
machine specs:
`===CPU:
model name : Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz
cpu cores : 2
model name : Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz
cpu cores : 2
model name : Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz
cpu cores : 2
model name : Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz
cpu cores : 2
===RAM:
total used free shared buff/cache available
Mem: 7,7G 1,8G 4,2G 316M 1,6G 5,3G
Swap: 29G 0B 29G
===OS:
Linux ferdinand-ubuntu 4.8.0-32-generic #34-Ubuntu SMP Tue Dec 13 14:30:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
`
Result here: https://imgur.com/5wZC8xi
I just know that caddy is not written in the c language so i think it doesnt outperform nginx.
written in go
Mmm my favorite. It’s the only web server config that I can consistently run purely from memory without bringing in reference sheets to supplement my memory.
Using a lower level language for a software means that there could be opportunities for a skilled developer to do certain things more efficiently, however this is not necessarily true in every case.
They realized their mistake and changed that. Caddy v2 is now free to use for any purpose, including commercial.
This benchmark was done with a pretty old version of Caddy and nginx. 2.0 is a much improved version of Caddy (according to the developer), and I'm sure nginx was improved since then as well.
According to my own very unscientific benchmark on a wordpress site running on single low-end VPS, nginx 1.18.0 and caddy 2.0.0 performed similarly. YMMV
Posted my Caddy v2 vs Centmin Mod Nginx benchmarks for both HTTP/2 & HTTP/3 over QUIC HTTPS at https://community.centminmod.com/threads/caddy-v2-versus-centmin-mod-nginx-http-2-http-3-https-benchmarks.19700/
enjoy
I tried this a few months back and I really like it. I liked the V1 too. It is so simple and fast to configure. I almost using Caddy permanently for one of my server, but turned out it make so many certificate request from Letsencrypt between my testing and reached limit. Took me a few hours to figure out why my HTTPS doesn't work. I wonder why there was no big warning about this LOL.
Also not all plugin from V1 available for V2. There was a plugin I want to have and V2 doesn't have it.
I ended up using NginX again.
@eva2000 , do you think the Caddy performance would hold up better if it were just used for SSL termination/proxy, and passing to Nginx after?
Thanks.
That would be like asking if a F1 racing car could hit 300+ km/hr if you put a VW Beetle in front of it
Really does depend on the server hardware/environment you pair a web server with and your specific work loads. It could be Caddy could handle your loads fine. Just you'd probably look at upgrading server hardware sooner with Caddy than you'd do with Nginx at very high concurrency user loads and traffic.
But can be mute point as these days folks would put Cloudflare proxy and it's caching in front your web server so scaling could be better. Though scaling is only good as how a server handles a cache miss (hit to origin backend)
yep i know it is not the c lang right?
I friggin love Caddy. It’s the perfect web server for easy reverse proxies and low traffic servers.
https://arstechnica.com/gadgets/2020/05/caddy-offers-tls-https-and-more-in-one-dependency-free-go-web-server/
A good article about Caddy v2 and Apache.
"The short version here is that Caddy wins. With a simple ab -c5 -t10 https://yourdomain.com/ running against a default virgin WordPress with the single Hello World post, Apache pulls 37.8 requests per second to Caddy's 42.4. Caddy also delivered slightly faster median requests, at 114ms to Apache's 129ms, and faster 99th percentile requests at 182ms to Apache's 184ms."