On Thu, Nov 19, 2020 at 6:25 AM Eric S Fraga <[email protected]> wrote: > > 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.
The 'TL;DR' brought a smile to my face. A friend and mentor often replied to short questions with 2 to 5 page emails and he used sure regularly! Sadly - - - - he died this May and boy do I miss his thinking - - - he called himself a computer dinosaur but his breadth of knowledge - - - - scary! > > 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). > I have long had the habit of backing up what I'm working on every 5 minutes. When I can I set this up in the software as an automated function. This kind of function just isn't in text editors so I do the manual saving. IN this way I do NOT have to fiddle fart with the system whining that I'm trying to overwrite the file, which I think I am actually doing, and the updated version is just 'saved'. What I would like is that file ledgerxxxxxxx.dat that I'm working on would be updated when I'm saving but not only to the one location but rather to 2 or 3 or 4 (how ever many I want) locations all at the same time, without having to argue with the system that I'm overwriting a file. The idea is NOT to save the file as a unique entity every number of minutes in each of a number of locations but rather to have one 'complete' file in each of x number of locations be updated simultaneously and easily. So far I'm not finding anything that's even remotely straight forward. >From what I understand - - - using rsync would spawn a plethora of versions meaning that I would have to create a timestamp on each to differentiate. Maybe, at least from my perspective, not the 'simplest' creation. The ideas presented are useful - - - but I'm hoping to find something just somewhat different (begging posture assumed - - - grin!). Regards -- --- 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/CAPpdf5_Cm_Bo%3DNrVN7PJ7NWdsjf_e1qixkSUwNHSAWj2-HU_Hg%40mail.gmail.com.
