How moor2006/waste-management works
This Flask application is a small waste-collection portal. Visitors can view the home page, submit collection requests, and access login, dashboard, tracking, complaints, and reports pages. The main data workflow stores submitted requests in SQLite and displays them on the dashboard; login checks SQLite user records. The source shows route and database behavior, but the templates were not inspected, so their internal behavior and the purpose of the tracking, complaints, and reports pages are unknown.
Main entry points: app.py Login route · database.db SQLite database · index.html Home page · login.html Login page
Components 16
Web routes
- Home route
app.py - Login route
app.py - Dashboard route
app.py - Collection route
app.py - Tracking route
app.py - Complaints route
app.py - Reports route
app.py
Page templates
- Home page
templates/index.html - Login page
templates/login.html - Dashboard page
templates/dashboard.html - Collection form
templates/waste-collection.html - Tracking page
templates/tracking.html - Complaints page
templates/complaints.html - Reports page
templates/reports.html
Persistence
- SQLite database
database.db
Other components
- Visitor
Connections 25
- Visitor → Home route: requests
app.py - Visitor → Login route: submits credentials
app.py - Visitor → Dashboard route: requests
app.py - Visitor → Collection route: submits request
app.py - Visitor → Tracking route: requests
app.py - Visitor → Complaints route: requests
app.py - Visitor → Reports route: requests
app.py - Home route → Home page: renders
app.py - Login route → Login page: renders
app.py - Login route → SQLite database: checks credentials
app.py - Login route → Dashboard route: calls on success
app.py - Dashboard route → SQLite database: reads requests
app.py - Dashboard route → Dashboard page: renders
app.py - Collection route → Collection form: renders
app.py - Collection route → SQLite database: stores submission
app.py - Collection route → Visitor: returns confirmation
app.py - Tracking route → Tracking page: renders
app.py - Complaints route → Complaints page: renders
app.py - Reports route → Reports page: renders
app.py - Home route → Visitor: returns page
app.py - Login route → Visitor: returns response
app.py - Dashboard route → Visitor: returns page
app.py - Tracking route → Visitor: returns page
app.py - Complaints route → Visitor: returns page
app.py - Reports route → Visitor: returns page
app.py