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
I feel like the /admin page has a lot of potential, but is currently very feature bare.
I had a few suggestions for ideas:
Two seperate sections for historical buckets and currently stored/active buckets
- It currently isnt clear what is and isnt active
A counter that shows how many times a bucket was downloaded
- Obviously only applies to none one-time-download buckets, but a true false on one time might be nice
The ability to "re enable" a one time download for a variable period of time
- Did a long slow one time upload recently only to have the user fail to download it due to a browser extension. This meant I had to reupload the data again. The ability to have say a 12 hour safetynet and re-enable the download would have prevented this
The ability to extend the retention period of a bucket
The ability to delete an active bucket maually, before it expires
Im unsure how difficult it would be to implement these, but it would take the admin page from being borderline useless to something incredibly useful.
The text was updated successfully, but these errors were encountered:
If an bucket is expired it will be deleted from disk. So backtracking isn`t posible
RP is created
See 1
the Authentication system is by design very very simple. But the password you enter by visiting the admin page is cached as long as you are on the admin page and will be available for request to update a bucket. I`m not sure if the repository owner wish that behavior
Hi
I feel like the /admin page has a lot of potential, but is currently very feature bare.
I had a few suggestions for ideas:
- It currently isnt clear what is and isnt active
- Obviously only applies to none one-time-download buckets, but a true false on one time might be nice
- Did a long slow one time upload recently only to have the user fail to download it due to a browser extension. This meant I had to reupload the data again. The ability to have say a 12 hour safetynet and re-enable the download would have prevented this
Im unsure how difficult it would be to implement these, but it would take the admin page from being borderline useless to something incredibly useful.
The text was updated successfully, but these errors were encountered: