Skip to content
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

Feature suggestion - /admin page overhaul #289

Open
jamess60 opened this issue Aug 15, 2023 · 1 comment
Open

Feature suggestion - /admin page overhaul #289

jamess60 opened this issue Aug 15, 2023 · 1 comment

Comments

@jamess60
Copy link

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:

  • 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.

@Maytrok
Copy link

Maytrok commented Nov 25, 2023

hi,

just my two cents.

  1. If an bucket is expired it will be deleted from disk. So backtracking isn`t posible
  2. RP is created
  3. See 1
  4. 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
  5. See 4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants