-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Golden Retriever] Ability to clear upload history or set expiry date #324
Comments
Hi! Golden Retriever is in beta mode and history clearing / expiry date is on our todo. Likely coming to a next version of Uppy (or the one after it) close to you! PRs welcome :) |
#349 will help with this by clearing files that are no longer related to any file in Two ideas for things we could do now:
There's an issue here about adding expiration to other storage forms, including indexeddb, which would be super nice: https://git.io/v5bau |
👍 3. We should also listen for |
Yep although I think we want to keep the thumbnails of completed uploads
…On 19 September 2017 00:39:11 CEST, Artur Paikin ***@***.***> wrote:
👍
3. We should also listen for `upload-complete` and delete the uploaded
file, right?
--
You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub:
#324 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
But then there’s no way to get rid of complete uploads? I think, maybe, once complete, it’s safe to not show it at all? |
Hmm yeah. I was thinking it'd make sense for thumbnails to keep showing if some of the files in a single we could address that more simply by listening for |
Expiry has landed in #369. Files will automatically be deleted after 24 hours by default. Blog post + docs for clearing manually, and setting a custom expiry timeframe, are coming up soon. Thanks! |
I have been testing Golden Retriever feature to restore files. I come to notice that it keeps history of all previous uploads. I was wondering if there is any proper way to clear the history or probably set some expiry date ?
The text was updated successfully, but these errors were encountered: