aboutsummaryrefslogtreecommitdiff
path: root/content/posts/2022-10-14-caddy.smd
diff options
context:
space:
mode:
Diffstat (limited to 'content/posts/2022-10-14-caddy.smd')
-rw-r--r--content/posts/2022-10-14-caddy.smd13
1 files changed, 13 insertions, 0 deletions
diff --git a/content/posts/2022-10-14-caddy.smd b/content/posts/2022-10-14-caddy.smd
new file mode 100644
index 0000000..009bf53
--- /dev/null
+++ b/content/posts/2022-10-14-caddy.smd
@@ -0,0 +1,13 @@
+---
+.title = "Caddy",
+.author = "Martin Ashby",
+.date = @date("2022-10-14T22:58:22+01:00"),
+.layout = "single.shtml",
+.custom = {"comments": true},
+---
+
+I switched to [caddy](https://caddywebserver.com) from nginx. Caddy has a 'simpler' configuration syntax, and offers built-in automatic TLS support with letsencrypt. I've also enabled automatic TLS support in [maddy](https://maddy.email) mail server, and I have been able to remove certbot entirely from my home server and disable the cron job that refreshed certs!
+
+The switch wasn't as painful as I thought it might be. It took about 45 minutes to read the caddy docs and port my existing nginx configuration over. Most of my sites are either simple static sites, or reverse proxies to other apps running their own web servers.
+
+This switch was prompted by a problem I've caused on my blog; I have put some large resources at my webserver root (e.g. /fooimage.jpg) instead of in a subfolder. In order to maintain external links, I wanted to move the images, and setup a permanent redirect to their new location. This is relatively difficult in nginx, and should be simpler in caddy.