You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Despite my 35TB library deletions are infrequent enough that I prefer to maintain control of the final "purge" process (I would still have to delete my download/cross-seed hardlinks orphans anyway).
The main drawback of staying in dry-run is that users don't receive notifications regarding seerr requests, but I can live with that.
I took a quick look at the code and I have a proposal.
Auto vs Manual deletion
Add a boolean config to toggle auto/manual deletion and check it before calling cleanupMedia().
So the whole cleanup job flow would ran, except for the purge.
Any thoughts? Or should I just disable dry-run, close my eyes and let go 😅.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm still running in
dry-runfor two reasons:The main drawback of staying in
dry-runis that users don't receive notifications regarding seerr requests, but I can live with that.I took a quick look at the code and I have a proposal.
Auto vs Manual deletion
Add a boolean config to toggle auto/manual deletion and check it before calling
cleanupMedia().So the whole cleanup job flow would ran, except for the purge.
Any thoughts? Or should I just disable
dry-run, close my eyes and let go 😅.Beta Was this translation helpful? Give feedback.
All reactions