From d188308d1faeb8494683613e572c478914dc1673 Mon Sep 17 00:00:00 2001 From: Waters Church Date: Thu, 24 Sep 2026 14:50:18 -0400 Subject: [PATCH] Version-control the backup LaunchAgent, with the path trap written down MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The plist existed only in the transfer bundle, in a version that still pointed at ~/Documents — the path that macOS TCC silently refuses to let launchd execute from, and the reason the nightly backup did nothing for eight days while logging nothing. Captured from the ingest Mac as it now runs, with a README explaining why the checkout must live outside ~/Documents and why the script cannot glob the Drive folder. Both are easy to undo by accident and expensive to rediscover. Co-Authored-By: Claude Opus 5 --- deploy/README.md | 32 +++++++++++++++ ....waterschurch.checklist-drive-backup.plist | 39 +++++++++++++++++++ 2 files changed, 71 insertions(+) create mode 100644 deploy/README.md create mode 100644 deploy/org.waterschurch.checklist-drive-backup.plist diff --git a/deploy/README.md b/deploy/README.md new file mode 100644 index 0000000..64c1f61 --- /dev/null +++ b/deploy/README.md @@ -0,0 +1,32 @@ +# Deployment bits that live outside the app + +## `org.waterschurch.checklist-drive-backup.plist` + +The LaunchAgent that runs the nightly off-site backup. It belongs in +`~/Library/LaunchAgents/` on **one** always-on Mac — currently the ingest Mac +(`NA-Ingest`, account `Studio`). Install with: + +```bash +cp deploy/org.waterschurch.checklist-drive-backup.plist ~/Library/LaunchAgents/ +launchctl load ~/Library/LaunchAgents/org.waterschurch.checklist-drive-backup.plist +``` + +**The path in it matters more than it looks.** It points at `~/checklist-app`, not +`~/Documents/…`, and that is not cosmetic: macOS TCC does not let `launchd` execute +anything inside `~/Documents`, `~/Desktop` or `~/Downloads`. When the project lived in +`~/Documents` the agent failed instantly every night with + +``` +/bin/bash: …/backup-to-drive.sh: Operation not permitted +``` + +logging nothing, for eight days, because the script never started. Keep the checkout +outside those folders on any machine that runs this agent. + +The same restriction applies one level down: `launchd` can stat a named file under +`~/Library/CloudStorage` but cannot list the directory, which is why +`backup-to-drive.sh` checks explicit filenames instead of globbing. + +A LaunchAgent only fires while that user is logged in. If the Mac is asleep at 04:15, +launchd runs the job shortly after it wakes, so a missed night self-heals — but a Mac +that is off, or logged out, backs nothing up and says nothing. diff --git a/deploy/org.waterschurch.checklist-drive-backup.plist b/deploy/org.waterschurch.checklist-drive-backup.plist new file mode 100644 index 0000000..fffcb00 --- /dev/null +++ b/deploy/org.waterschurch.checklist-drive-backup.plist @@ -0,0 +1,39 @@ + + + + + Label + org.waterschurch.checklist-drive-backup + + ProgramArguments + + /Users/Studio/checklist-app/backup-to-drive.sh + + + + StartCalendarInterval + + Hour4 + Minute15 + + + RunAtLoad + + + + StandardOutPath + /Users/Studio/Library/Logs/checklist-drive-backup.out.log + StandardErrorPath + /Users/Studio/Library/Logs/checklist-drive-backup.err.log + + + EnvironmentVariables + + PATH + /usr/local/bin:/opt/homebrew/bin:/usr/bin:/bin:/usr/sbin:/sbin + + +