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
New option in Settings to remove automatically all the downloaded and temporal stuff from the local storage. Where to place? i'd go for the Advanced section. Option called Delete local copies, that will display the proper options.
Proposal:
never
1 hour
12 hours
1 day
30 days
The way to display could be an slider like in iOS, but other options are also valid, f. ex. something similar to the Security > Lock application option.
A worker will run with the given frequency and will delete those files which last_usage date is older than the given time. This is only an approach (any ideas to improve?). Removing tmp and failed uploads as well.
Check frequency of the worker (¿¿1 hour??)
Check if feasible to check if file is being previewed (to avoid being deleted while previewing)
/tmp directory contains on the one hand temporal files related to uploads (which we shouldn't remove in case they're failed uploads, more info: #4320 (comment)), and temporal files related to downloads. For this issue we'll just deal with downloaded files, not the /tmp directory, we'll research more about this in another issue
EPIC:
Context: #4002 (comment)
New option in
Settings
to remove automatically all the downloaded and temporal stuff from the local storage. Where to place? i'd go for theAdvanced
section. Option calledDelete local copies
, that will display the proper options.Proposal:
The way to display could be an slider like in iOS, but other options are also valid, f. ex. something similar to the
Security > Lock application
option.A worker will run with the given frequency and will delete those files which
last_usage
date is older than the given time. This is only an approach (any ideas to improve?). Removing tmp and failed uploads as well.iOS style (right screenshot): #4002 (comment)
TASKS
The text was updated successfully, but these errors were encountered: