avoid removing too many ZIMs at once => this is a bit blurry, but the scenario I have in mind is that should we publish an empty catalog for any reason (or should the program believe the catalog is empty for any reason), it would be a pity / concern to cause all ZIMs of all peers to be deleted within few hours ; maybe even deleting too many ZIMs at once is an indicator of an issue ; that been said, since we keep the ZIMs for --keep days, the impact is obviously not immediate ... should we simply have an alerting system? a summary file one can watch with details about files which are going to be removed in 1 week, 2 weeks, 4 weeks, 8 weeks, 12 weeks?
Originally posted by @benoit74 in #6 (review)
Originally posted by @benoit74 in #6 (review)