{"id":48892,"date":"2020-05-13T05:02:55","date_gmt":"2020-05-13T03:02:55","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=48892"},"modified":"2020-05-13T05:02:55","modified_gmt":"2020-05-13T03:02:55","slug":"caddy-the-ultimate-server-with-automatic-https","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2020\/05\/13\/caddy-the-ultimate-server-with-automatic-https\/","title":{"rendered":"Caddy – The Ultimate Server with Automatic HTTPS"},"content":{"rendered":"\n

Great things are easy to get used to.\u00a0 When something works the way you want it, and does so for a long a time, it is inevitable that one day you’ll stop thinking about it altogether and accept it as a given.<\/p>\n

Apache was a great web server, until Nginx came along.\u00a0 All of a sudden, it became obvious how much faster things could be, and how much simpler the configuration file is possible.<\/p>\n

For the last few years, Nginx was working great for me.\u00a0 And now that I came across Caddy<\/a>, I realized that life can be a lot simpler.<\/p>\n

\"Caddy<\/a><\/p>\n

Here’s a bit to get you started:<\/p>\n

Caddy simplifies your infrastructure. It takes care of TLS certificate renewals, OCSP stapling, static file serving, reverse proxying, Kubernetes ingress, and more.<\/p>\n

Its modular architecture means you can do more with a single, static binary that compiles for any platform.<\/p>\n

Caddy runs great in containers because it has no dependencies\u2014not even libc. Run Caddy practically anywhere.<\/p><\/blockquote>\n

Seriously? We now have a web server which handles HTTPS with automatically renewed certificates (yes, Let’s Encrypt) out of the box… Mind-blowing.\u00a0 I guess, 21st century is indeed here now.<\/p>\n

What else is there?\u00a0 Well, let’s see:<\/p>\n