Uses
Hardware
- Laptop
- ThinkPad T14 Gen 3, 32 GB RAM, Debian testing. The only machine I carry.
- Home lab
- Two mini-PCs (N100, 16 GB each) and one old Xeon that exists for testing certificates and bad ideas.
- Phone
- A Pixel with too many VPN clients installed. Useful for reproducing what customers see.
- Network
- MikroTik hEX at home, because a router that can show a packet is worth more than one with a nice app.
Software
- OS
- Debian stable on servers, testing on the laptop. Ubuntu where the vendor only supports Ubuntu.
- Firewall
- nftables, always with a config file in git. Fail2ban or CrowdSec depending on what is already there.
- Web
- nginx for reverse proxying and static files. Caddy when certificates should be somebody else's problem.
- Tunnels
- Xray with Reality for censored networks, WireGuard for everything internal.
- Backups
- restic to a second provider. A cron job that writes one line to a log, and a Monday habit of reading it.
- Monitoring
- Prometheus, node_exporter, Grafana for graphs, and a small Python script for checks that do not fit.
- Terminal
- tmux, ssh, tcpdump, ss, mtr, jq. Nothing exotic.
- Notes
- Markdown files in a git repository, one directory per machine. Searchable with grep, which is the only search that survives a decade.
What I refuse to use
Web-based server panels on customer machines, "smart" backup appliances, and anything that hides the routing table behind a GUI. If a system cannot be fixed over SSH with a rescue shell, it is not a system I want to be responsible for.