- re: Obsidian scheduled backups - Tried to get
launchdto work viaplistat~/Library/LaunchAgents/com.gilite-notes.notes.plist, but it didn't have enough permissions to access the Node files at/usr/local/bin/node.- Originally preferred
launchdovercronsince it allows the job to run right after the computer wakes from sleeping, if the job was supposed to run but the computer was in sleep mode. - Also attempted moving the plist to
~/Library/LaunchDaemons/so that the job can be executed even if I'm logged out, but the same error as above occurred. cronworked after a few tries, incl. setting the git config to replacehttps://github.com/with[email protected]:since one of the errors specifiedfatal: could not read Username for 'https://github.com': No such file or directory. (see this)- To get over the same error with
launchd, grant cron 'Full Disk Access' at Security & Privacy in macOS. - The cronjob can be edited via
crontab -e, while list of cronjobs can be outputed viacrontab -l. Cronjob outputs can be viewed withmail.
- Originally preferred
- re: UPDATE on ^ - Got
launchdto work! The issue was the same; enable 'Full Disk Access' forlaunchctl- Remember to execute the following load and unload commands every time you make a change to the plist file:
launchctl unload ~/Library/LaunchAgents/com.gilite-notes.notes.plistlaunchctl load ~/Library/LaunchAgents/com.gilite-notes.notes.plist
- Test the plist file by manually triggering it:
launchctl start com.gilite-notes.notes
- Check if the plist file is valid:
plutil ~/Library/LaunchAgents/com.gilite-notes.notes.plist
- Remember to execute the following load and unload commands every time you make a change to the plist file:
- There's a collection of OSS on Code Shelter for volunteer devs to adopt projects as maintainers.
Whoops skipped TIL for this day