Tootfinder

Hmm I kinda wish the #dirvish extension had submitted fixes and enhancements to the #upstream project rather than just lift and shifted the code. At least the license is the same:

@… @… I used to do this but then I started to wonder what happens to my site during rsync? Could a visitor see a broken site? What happens if I lose connectivity in the middle of a deploy? What happens if the deploy fails (for any number of reasons)? …

I lost a lot of work by accident that I didn't push yet. 🥲
And I excluded them from #backups because I thought that I'd #push and publish them "soon" anyway.
All it took was a mistake when running #rsync

Resilient technologies aren’t retro—they’re ROOT: Robust, Open, Ongoing, Time-tested. In RDM, text-first small, composable tools beat opaque stacks. Emacs/Org(-babel) for literate workflows & provenance; Makefiles declare rebuilds; CLI atoms—curl, sed, awk, grep, diff, tar, rsync, cron, SQLite—keep steps inspectable, portable, rebuildable. DOI: https://

@… tipped me of to the best rsync tip. Always . at the end of your paths to remove the "is this gonna sync the directory and it's contents or the contents of this directory" ambiguity
`rsync -avsPW host:/path/. data/.`
(how the hell did I typo the original version of this? Fixed.)

🌐 #Tailscale VPN integration with pre-auth key support & custom server options
💾 Automated #rsync backups over SSH with cron scheduling & ntfy/Discord notifications
🔧 Kernel hardening via sysctl, swap file setup & Lynis/debsecan security audits
📋 Idempotent, produ…

rsync tip: if you're going to
--delete,
do
--dry-run
first.