How gamestar911/todocker works
This Flask application supports account-based and API-driven CSV classification, plus analysis history, API-key management, password recovery, and a Grok-backed chatbot. The main workflow is upload, validate and train, then return accuracy and a confusion matrix for display. The sampled code shows the Flask routes and runner; some documented capabilities are represented at their supported enclosing path because their implementation details were not sampled.
Main entry points: app.py Flask routes · logistics_runner.py Classification runner · dashboard.js Analysis client · chatbot.js Chat screen
Components 17
Web experience
- Browser UI
templates/dashboard.html - Analysis client
static/js/dashboard.js - Flask routes
app.py - Account screens
templates/form2.html
Dataset analysis
- Classification runner
logistics_runner.py
Accounts and data
- API-key validation
app.py - Account and analysis records
app.py - SQL database
- Password recovery
app.py - Email delivery
app.py - Analysis history
templates/analysis_history.html - API-key screens
templates/api_keys.html
AI assistant
- Chat screen
static/js/chatbot.js - Chat endpoint
app.py - Grok service
Other components
- User
- API client
Connections 28
- User → Browser UI: uses
- Browser UI → Analysis client: loads
- Analysis client → Flask routes: posts dataset
- Flask routes → Classification runner: runs experiment
- Classification runner → Flask routes: returns metrics
- Flask routes → Analysis client: returns results
- API client → API-key validation: submits dataset
- API-key validation → Account and analysis records: validates key
- API-key validation → Classification runner: runs experiment
- Classification runner → API-key validation: returns metrics
- User → Account screens: uses
- Account screens → Flask routes: submits credentials
- Flask routes → Account and analysis records: reads and writes
- Flask routes → Password recovery: handles reset
- Password recovery → Email delivery: sends reset message
- Email delivery → User: delivers email
- User → Analysis history: views records
- Analysis history → Flask routes: requests history
- Flask routes → Account and analysis records: loads history
- User → API-key screens: manages keys
- API-key screens → Flask routes: requests key actions
- Flask routes → Account and analysis records: stores key records
- Account and analysis records → SQL database: reads and writes
- User → Chat screen: asks question
- Chat screen → Chat endpoint: posts message
- Chat endpoint → Grok service: sends prompt
- Grok service → Chat endpoint: returns response
- Chat endpoint → Chat screen: returns answer