8000
Add retention settings for database records and pre-migration backups · Issue #1344 · slskd/slskd · GitHub
More Web Proxy on the site http://driver.im/
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
Here are the retention settings at the time of writing:
retention:
search: 10080# 7 days, in minutestransfers:
upload:
succeeded: 1440# 1 day, in minuteserrored: 30cancelled: 5download:
succeeded: 1440# 1 day, in minuteserrored: 20160# 2 weeks, in minutescancelled: 5files:
complete: 20160# 2 weeks, in minutesincomplete: 43200# 30 days, in minuteslogs: 180# days
The transfers retention settings dictate when records are removed from the UI, not the database; records are retained forever. As the application ages, high-volume users will likely need a way to clean this data up to control database size.
Additionally, I'm working on a feature that adds database migrations, and prior to performing migrations database backups are taken. These backups will double the size of database storage, and unless data was lost or mangled by a migration the backups are of little use and should be deleted.
Add a section to retention options, like:
retention:
database:
transfers: <duration to retain individual records>... other tables ...backups: <duration to keep pre-migration backups>
And of course, the logic that will actually do the cleanup will be needed as well.
The text was updated successfully, but these errors were encountered:
Here are the retention settings at the time of writing:
The
transfersretention settings dictate when records are removed from the UI, not the database; records are retained forever. As the application ages, high-volume users will likely need a way to clean this data up to control database size.Additionally, I'm working on a feature that adds database migrations, and prior to performing migrations database backups are taken. These backups will double the size of database storage, and unless data was lost or mangled by a migration the backups are of little use and should be deleted.
Add a section to retention options, like:
And of course, the logic that will actually do the cleanup will be needed as well.
The text was updated successfully, but these errors were encountered: