How pentester-kg/debttracker works
This is a Django debt-tracking application. Its main workflow routes requests for a debt list, detail, creation, update, or deletion to class-based views; those views query or modify Debt records and render debt templates. The repository also registers debts in Django admin and defines a separate form with field validation, though the sampled views do not use that form. Source excerpts show the SQLite configuration and the routing, model, and view relationships; template contents and database operations are not shown.
Main entry points: models.py Debt model · views.py Debt views · app/urls.py Debt routes · config/urls.py Project routes
Components 8
Request routing
- Project routes
config/urls.py - Debt routes
app/urls.py
Debt workflow
- Debt views
app/views.py - Debt validation form
app/forms.py - Django admin
app/admin.py
Debt data
- Debt model
app/models.py - SQLite database
config/settings.py
Rendered interface
- Debt templates
templates/debts
Connections 7
- Project routes → Debt routes: includes
config/urls.py - Debt routes → Debt views: routes to
app/urls.py - Debt views → Debt model: queries and mutates
app/views.py - Debt views → Debt templates: renders
app/views.py - Debt validation form → Debt model: validates model
app/forms.py - Django admin → Debt model: registers
app/admin.py - SQLite database → Debt model: configures storage