What Admin functionality is available?

[FoxxMD]

I know it's early days but I don't see this information in the docsite or easily discoverable in the repo.

As a self-hoster/admin of yeetfile what kind of functionality do I have available for adminstration of accounts and content?

Obviously, I can't see the actual content being uploaded. But these things come to mind for general maintenance, safety, etc...

• There is no UI for admin tools (that I can see), is everything done through the cli/tui?
  • What is the name of the cli/tui? Is it provided as part of the container? How do I access it?
    • EDIT: I dug into the code -- cli is not included in docker image. It is for the end-user offering the same functionality as the web ui. No admin functionality.
• Can I see account id/emails as a list? Is there a way to deactivate/delete accounts?
  • Is there a way to deactive/delete all content related to a specific account?
• What detail is available about individual content uploads?
• Can I delete/deactivate individual uploads? Can I identify an upload for a specific user?
  • EX user forgets password and wants to delete 5GB uploaded file
• Does the app or docker container output any logs when auth-related actions fail?
  • For instance, I would want to fail2ban/crowdsec ban an IP that tries to bruteforce the signup password, an upload's password, or bruteforce finding uploads by trying random URLs

[benbusby]

Right now administration of accounts and content isn't available through a UI, you would basically need to do interact with the database for things like deleting accounts or deleting content related to an account.

Can I see account id/emails as a list? Is there a way to deactivate/delete accounts?
Is there a way to deactivate/delete all content related to a specific account?
Can I delete/deactivate individual uploads?

These are all situations where you'd need to manually view/edit/delete entries in the database. I'm interested in making an admin UI for these sorts of actions, and will prioritize that for the next feature.

What detail is available about individual content uploads?

For uploads to the file vault, instance admins are only able to see general metadata for files that a user has uploaded. This includes:

• An encrypted file name (admin can't decrypt)
• The size of the file
• When it was uploaded

This information should be good enough to handle the situation you mentioned where a user forgets their password and wants to delete a 5GB file. Although in that case, it might just be better to delete their whole account if they have no way of recovering their password anyways.

EDIT: File uploads to YeetFile Send are not tied to user account IDs, so would not be a candidate for managing from an admin UI. I assume this is not a huge deal though, given the ephemeral nature of the uploads to Send.

Does the app or docker container output any logs when auth-related actions fail?

Auth actions don't explicitly log failures, they just return the error to the client. I'll add some logging for these scenarios. That said, there is middleware for auth endpoints that limits the number of times both signup and login can be performed from a single IP. Right now it's hardcoded to a maximum of 6 attempts in 30 seconds, which gets reset if another attempt happens during the cooldown. It would probably be better to allow that to be configured with environment variables though, so I'll make a note of that too.

I appreciate the questions, it's quite helpful to know what's important to others so that I can start adding features while YeetFile is still in a "version 0" state.