feat: Add User Management and Admin Dashboard#1
Conversation
- Introduce Viper for server configuration (`--config`, `listen_address`, `master_token`). - Isolate keys in BadgerDB via prefixes (`content:`, `metadata:`, `user:`, `token:`). - Limit `POST /` uploads to authenticated users with `X-API-Token` header. - Add simplistic `/admin` panel protected by master_token session login. - Support creation, listing, content inspection, and deletion of users. Co-authored-by: RdrSeraphim <8297347+RdrSeraphim@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
This PR introduces an authentication and barebones user management system. Uploads now require an
X-API-Tokenheader. Users and metadata are managed using structured key prefixes in BadgerDB to ensure safe isolation. An HTML admin dashboard was added at/admin, protected via a session cookie issued upon login with amaster_tokendefined in the application's configuration. The server configuration is now managed by Viper, supporting.yamlfiles from standard config locations.PR created automatically by Jules for task 12502067831360256290 started by @RdrSeraphim