@ -32,11 +32,7 @@ With my server locked down (let's pretend that's the first thing I did, like it
In my previous attempts at hosting things myself, I had fumbled through nginx reverse-proxy tutorials. While nginx is a great skill to learn, and an incredibly mature tool, I decided to take a different route this time and use Caddy. I acknowledge that nginx is great technology, but after using it on this server I am officially sold on Caddy.
In my previous attempts at hosting things myself, I had fumbled through nginx reverse-proxy tutorials. While nginx is a great skill to learn, and an incredibly mature tool, I decided to take a different route this time and use Caddy. I acknowledge that nginx is great technology, but after using it on this server I am officially sold on Caddy.
<img
src="/caddy-best-friend.jpg"
alt="friendship ended with nginx, now caddy is my best friend"
style="width: 400px; height: auto;"
/>
The two reasons I love Caddy are its [super easy configuration](https://caddyserver.com/docs/caddyfile) and its [automatic https](https://caddyserver.com/docs/automatic-https). The biggest challenges I had with hosting things myself in the past is partially my poor nginx configuration abilities, but largely that messing with [certbot](https://certbot.eff.org/) (an admittedly great and easy to use project) was a lot more work than I wanted to constantly manage for every single project that I wanted to host. HTTPS is a process that can be automated, and Caddy proves that. Now, I simply add a new site configuration block to my `Caddyfile` and I already automatically have HTTPS for that site (provided the domain name I specified has DNS configured correctly, more on that later).
The two reasons I love Caddy are its [super easy configuration](https://caddyserver.com/docs/caddyfile) and its [automatic https](https://caddyserver.com/docs/automatic-https). The biggest challenges I had with hosting things myself in the past is partially my poor nginx configuration abilities, but largely that messing with [certbot](https://certbot.eff.org/) (an admittedly great and easy to use project) was a lot more work than I wanted to constantly manage for every single project that I wanted to host. HTTPS is a process that can be automated, and Caddy proves that. Now, I simply add a new site configuration block to my `Caddyfile` and I already automatically have HTTPS for that site (provided the domain name I specified has DNS configured correctly, more on that later).
