Hacker News Reader

Comment by nasdack | Hacker News Reader

> 3. Obsess about backing up all of your org files because if you ever lose them you will literally have lost half of what you know.

Do you use version control to backup org-mode, or opt for some Google Drive/Dropbox/Nextcloud scheme?

View on HN

I don't trust myself to remember to commit changes, so rely on regular btrfs-based snapshots via http://snapper.io/ .

For other uses, I’ve defined cronjobs similar to:

  0 0 * * * cd /foo; git add -A && git commit -m $(date) && git push

Voila! Nightly snapshots pushed to another server.

I use syncthing on a NAS device in my house. That's a 2-bay NAS in RAID 1 configuration.

All machines I want to use the files from need to use syncthing pointed at the NAS folder. The NAS basically becomes my central repository of files.

TODO! Backup the NAS to somewhere offsite. Maybe an S3 bucket or google cloud storage or something.

Although git works great, there is some double-duty regarding history: there are both the git history of the .org files and also the.org_archive files. I wonder if people opt for one or the other and not both?

I've been using Org Mode for close to 10 years now, and I never grokked how the archiving is supposed to be used. You can browse the archive files for your data, and the automatically added metadata give some context as to where it was located, but AFAIK you can't rebuild an old version of an .org file from the archive. So because of that, if I care about the whole structural history of an org file, I stick it in a git repository.

I made a thread about this on /r/Emacs, perhaps people here might chime in too: https://old.reddit.com/r/emacs/comments/jiyn4n/orgmode_archi...

Reply on news.ycombinator.com