How daniel-c-silva/plume works
Plume currently implements a basic account-registration flow: a user submits username and password in the React registration form, which posts to Flask; Flask hashes the password and stores the account in PostgreSQL, then returns feedback for display. The database initializer also defines an answers table and a per-user question counter, but no answer-handling workflow is shown. App.jsx is a separate Vite/React starter screen, not imported by the sampled entry point. The map reflects shown code; no broader product capabilities are documented in the provided README.
Main entry points: app.py Registration API · main.jsx Registration form · db.py DB initializer
Components 6
Client
- Registration form
frontend/Plume/src/main.jsx - Starter screen
frontend/Plume/src/App.jsx
Registration backend
- Registration API
backend/app.py
Persistence
- DB initializer
backend/db.py
Other components
- User
- PostgreSQL
Connections 6
- User → Registration form: submits credentials
frontend/Plume/src/main.jsx - Registration form → Registration API: posts registration
frontend/Plume/src/main.jsx - Registration API → DB initializer: initializes and connects
backend/app.py - DB initializer → PostgreSQL: creates tables
backend/db.py - Registration API → PostgreSQL: inserts account
backend/app.py - Registration API → Registration form: returns feedback
frontend/Plume/src/main.jsx