TL;DR: I use a combination of git (as Boyd has suggested, committing changes every transaction) and rsync to back up to a different device.
Longer version: there are 2 different issues here: 1. micro-management of information, e.g. changes and reasons for those changes 2. keeping back ups in case of hardware/software/user failure (e.g. rm) Different tools are appropriate for each of these but both of these issues are important in their own right. For 1, version (or revision) control systems are ideal. There are many, including git, mercurial, subversion, src, rcs, ... Each of these has their respective advantages and disadvantages and personal taste often is the deciding factor. I use src for single file revision control and git for projects. They do not provide more than simple backup but do provide the ability to roll back changes and an audit trail. For 2, I would avoid the use of symlinks and instead ensure you have a proper more general backup procedure. For instance, I rsync my whole disc to a different computer in a different site frequently (hourly often but at least once a day in any case) during the day and I do full scheduled backups onto detachable drives periodically (weekly or monthly depending on how I feel). -- Eric S Fraga via Emacs 28.0.50 & org 9.4 on Debian bullseye/sid -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ledger-cli/87blft5y9l.fsf%40ucl.ac.uk.
