Notes Archive

A practical list for low-maintenance servers: package cadence, basic logs, renewal reminders, and a bias toward plain services over clever stacks.

I keep a tiny changelog for every host, standardize service names, and avoid one-off edits that only make sense in the moment.

Write down purpose, source, destination, and rollback plan before changing exposure. It takes two minutes and saves an hour.

No database, low maintenance, easy backups, and the content stays readable years later. That trade still feels right.

Even tiny utilities benefit from clear entry points, obvious config, and a short README that explains what problem they actually solve.