dem vielen Wasser, das hier überall auf Wiesen und Feldern steht
meiner Affinität zu Keyboards als primäres Interaktionselement mit Computern …
… und welchen Keyboard-Shortcut ich in Firefox schmerzlich vermisse
der macOS App Rectangle
dem Fork von nginx zu freenginx und wie ich am Wochenende nach 19 Jahren ausschließlich nginx-Nutzung mit Caddy erstmals einen anderen Webserver angeschaut habe und seit dem ziemlich begeistert bin
einer Anleitung wie man gute technische Dokumentation schreibt
mkcert und wie es xca als Management-Tool für meine lokale CA abgelöst hat
If anyone has successfully gotten Peertube working on NixOS with Caddy, please message me. I've tried both Podman and the official NixOS packaging of it, and the farthest I've gotten is OAuth bitching about the externyal domain not being identical to the internyal IP. (If I configure the instance domain to be vcr.sbargv2.com, it throws a tantrum that it's not 192.168.86.38. If I set the instance domain to be 192.168.86.38, it throws a tantrum that it's not vcr.sbargv2.com) #caddy#nixos#peertube#selfhosted#askfedi
I'm sorry but the #Caddy exposed metrics are just … bad.
Values were not matching up at all until I realize that I can't filter the Caddy metrics per vhost, so I'm probably seeing the effect of the websocket connected for goaccess (which I'm also not fond of, but it just gained a cookie by demonstrating me this problem.)
This version uses the brand-new #Caddy server 2.7 and slightly improves resource consumption by exploiting the new features introduced in #golang 1.20.
After spending a good few hours trying to get an nginx reverse proxy app (docker, say no more) to start working again, I've just discovered #Caddy.
For goodness sakes, it wasn't ever meant to be this easy!
Anyone know, does #Caddy strip trailing periods and spaces from paths of requests it proxies upstream? #Nginx does this on Windows for… reasons, and you can't turn it off.
I first starting tinkering with Caddy (the web server) when I hosted my own Mastodon instance, but my tinkering really only involved copying and pasting someone else's working configs.
After running it at home for some personal infrastructure, I'm really impressed. The config is quite minimal and lots of things I normally need to configure (like HTTPS redirects) are there right out of the box. 👏
Also, the easiest part in the whole setup was – as always – #Caddy. Took like five minutes to set it up as the reverse proxy, including fully automatic HTTPS certificates.
Honestly I haven’t been using Apache or nginx for years, and there’s nothing that I miss. Caddy is so easy to install (single binary), set up (five lines of configuration often suffice) and just works. Check it out if you’ve never used it, you might be never going back to anything else.