- Spurn ~. It generally gets cluttered with machine specific stuff.
- The primary goal is to preserve knowledge.
- The data should be easily readable in 20 years time on hw/sw not yet invented.
My 'digital life' goes in its own folder (eg /foobar), which is Syncthing'ed around to various machines, and backed up periodically. It's very big, and contains a snapshot of 'everything' I want to preserve.
Cron run various scripts to pull data from multiple services (e.g. Pinboard, DayOne, etc) so if they ever go down, I have the data I created on them.
I segment documents and projects that I create / work on from those I've just downloaded to use. This results in a fairly simple top level folder structure:
- docs: Documents and textual data
- dev: Projects, design work, development etc
- external: External tools, software, etc
- media: mostly video/audio
Projects of course do live in their own git repos.
Tools:
- Emacs org mode for notes, todos, etc (best in class)
- DayOne for journaling and notes while mobile
(integrated with org notes)
- Pinboard bookmarks
I'm not a huge fan of using fancy project management software tools, because fashions change, tools go out of date, data gets lost etc. Straightforward text files for most things is the best combination of usability and persistence for me. Wikis are great, but suffer from this - they need maintaining, software needs updating, the database format could change, etc. A bit of work to get a text based system going is totally worth it ;).
I haven't used it with very large files (100mb pdf is the largest thus far), but I've had problems with making sure every client has the same version. SyncThing doesn't sync with those using a different major version, and some SyncThing wrappers aren't as good as others with keeping itself up-to-date.
This resulted in a merge conflict with a large KeePassX db file x_x
I haven't had any issues with SyncThing so far, other than the initial setup faff! I haven't had to deal with any horrible merges, and as long as you take frequent snapshots you should be able to recover if the worst happens.
- Spurn ~. It generally gets cluttered with machine specific stuff.
- The primary goal is to preserve knowledge.
- The data should be easily readable in 20 years time on hw/sw not yet invented.
My 'digital life' goes in its own folder (eg /foobar), which is Syncthing'ed around to various machines, and backed up periodically. It's very big, and contains a snapshot of 'everything' I want to preserve.
Cron run various scripts to pull data from multiple services (e.g. Pinboard, DayOne, etc) so if they ever go down, I have the data I created on them.
I segment documents and projects that I create / work on from those I've just downloaded to use. This results in a fairly simple top level folder structure:
- docs: Documents and textual data
- dev: Projects, design work, development etc
- external: External tools, software, etc
- media: mostly video/audio
Projects of course do live in their own git repos.
Tools:
- Emacs org mode for notes, todos, etc (best in class)
- DayOne for journaling and notes while mobile (integrated with org notes)
- Pinboard bookmarks
I'm not a huge fan of using fancy project management software tools, because fashions change, tools go out of date, data gets lost etc. Straightforward text files for most things is the best combination of usability and persistence for me. Wikis are great, but suffer from this - they need maintaining, software needs updating, the database format could change, etc. A bit of work to get a text based system going is totally worth it ;).