It seems that this plugin will be used so I added the appropriate first post to add it to the plugin index.
As for how many backups to keep, this is made a bit complicated by the fact that other files can exist in the backup folder. I can't scan for a certain time and delete if older. I can work around this by keeping a list of backups, but this suffers from itself being a config preference. If a config is restored the preference will be as well, probably orphaning some files. The user will be required to look and clean from time to time.
I will add two configuration lines:
- Days to keep all backups: [N] (default 3)
- Days to keep last backup: [N] (default 10)
Reasoning: if something goes wrong then having access to all the latest config backups for a few days could be a life saver because you don't know when things broke. For older backups, the last of the day will be sufficient.
And yes, to restore a backup, close calibre then extract the zip file into the configuration folder. To be the most safe, rename the config folder, create a new one, then extract the zip. This ensures that no "extra" config files are left over. This "restore" can't safely be done inside calibre.
Quote:
Originally Posted by Comfy.n
(yet I've never had issues after restoring backups made with the script I run, which most times I do with Calibre running  ) |
Calibre will save config information using in-memory values. Changes made to config files will be lost in this case.