to host my own outline
Outline is a very fast, very pretty notes/wiki system, and I've got my very own now.

Outline is a very fast, very pretty notes/wiki system, and I've got my very own now.

I use fail2ban as my server watchdog. Among the sensible defaults it hands me is a file path pattern that uses a wildcard to hoover up my nginx access logs:
nginx_access_log = /var/log/nginx/*access.log
Super convenient, except that pattern gets evaluated when fail2ban starts up, and never again. If your server starts writing more logs that match the pattern — say if you launch a new site and direct its logs to a new file — your fail2ban jails that use the nginx_access_log path variable won't see them until it restarts. And then you'll be looking at the server logs and the ban logs and testing things with fail2ban-regex and have no idea why people doing bannable things are not getting banned.
Anyway restart fail2ban sometimes. You know, just in case.
from @ello@void.ello.tech
I've been using Mail-in-a-Box to self-host my own email and DNS for about four-ish years. I got in before VPS providers started cracking down on SMTP traffic, and I've been pretty happy with the experience. Except for the time I procrastinated upgrading so far that I had to get upgrade instructions off the Wayback Machine, but that was my own fault.
Mail-in-a-Box comes configured with a Munin installation. I'd never really touched it beyond browsing the graphs and hmmm-ing sagely, but as I was moving a bunch of other servers around I realized that Munin is intended to aggregate monitoring from a whole network, not just one server. I had five servers scattered around doing things like hosting websites and serving Steam games, so hooking them up to a monitoring hub seemed like a win.