Quote:
Originally Posted by JimmXinu
...
Re: Built-in backup, as edeniz said, the first line of defense is 'update epub if new chapters'. The second line of defense, IMO, is your own regular backups--everybody has those, right?
...
I believe 'backups' have been requested before and I rejected the idea as outside scope and a bit of a slippery slope. If one backup, why not the last 2? Or 3? What about comparing to show what's changed between backup and current? Etc, etc.
|
I explained why the first line of defense doesn't always work. Keeping manual backups is sensible yes, but if you have a library exceeding a certain size and, like me, regularly update a bunch of stories fully to archive changes to old chapters, you'll be hard pressed to figure out if a story suddenly changed in an unfavorable way without checking every single story each time -- it would be a huge chore.
Regarding the backups: I always thought it obvious to keep a backup for every single revision, not just a single backup. Manual purging would have to be done at some point somehow, but this seems much nicer to me than the other solution.
For now I'll simply use
borgbackup to create incremental and really regular backups of my Calibre library. Ideally I want to figure out a way to hook into Calibre's book modification mechanism and write a plugin centered around backups and possibly comparing/restoring revisions (maybe).