How dormouse-925/tp_coo works
Velos is a Django application for representing production, supply, and retail entities and calculating costs. Its visible user-facing workflow routes country and city detail requests to JSON views, which serialize model data; Django admin also exposes the domain models for management. The models cover locations, production operations, products, inventory, and sales records. The repository also contains a separate tp-coo greeting stub, but it does not appear connected to Velos. The README is empty, so capabilities and links here are limited to the supplied source excerpts.
Main entry points: admin.py Model admin · db.sqlite3 SQLite database · models.py Production locations · settings.py Django settings
Components 18
Web access
- URL routes
velos/velos/urls.py - Detail views
velos/high_level/views.py - Model admin
velos/high_level/admin.py
Cost domain
- Country and city
velos/high_level/models.py - Production locations
velos/high_level/models.py - Machines and quantities
velos/high_level/models.py - Production operations
velos/high_level/models.py - Products and pricing
velos/high_level/models.py - Suppliers and transport
velos/high_level/models.py - Stock quantities
velos/high_level/models.py - Sales locations
velos/high_level/models.py - Customer invoices
velos/high_level/models.py
Persistence and runtime
- SQLite database
velos/db.sqlite3 - Django settings
velos/velos/settings.py - ASGI entrypoint
velos/velos/asgi.py - WSGI entrypoint
velos/velos/wsgi.py
Other components
- API client
- Admin user
Connections 35
- API client → URL routes: requests
velos/velos/urls.py - URL routes → Detail views: routes to
velos/velos/urls.py - Detail views → Country and city: loads and serializes
velos/high_level/views.py - Admin user → Model admin: manages
velos/high_level/admin.py - Model admin → Country and city: registers models
velos/high_level/admin.py - Model admin → Production locations: registers models
velos/high_level/admin.py - Model admin → Machines and quantities: registers models
velos/high_level/admin.py - Model admin → Production operations: registers models
velos/high_level/admin.py - Model admin → Products and pricing: registers models
velos/high_level/admin.py - Model admin → Suppliers and transport: registers models
velos/high_level/admin.py - Model admin → Stock quantities: registers models
velos/high_level/admin.py - Model admin → Sales locations: registers models
velos/high_level/admin.py - Model admin → Customer invoices: registers models
velos/high_level/admin.py - Production locations → Country and city: references city
velos/high_level/models.py - Production locations → Machines and quantities: costs quantities
velos/high_level/models.py - Machines and quantities → Production operations: supplies machine cost
velos/high_level/models.py - Production operations → Products and pricing: costs product operations
velos/high_level/models.py - Suppliers and transport → Products and pricing: prices products
velos/high_level/models.py - Stock quantities → Products and pricing: costs quantities
velos/high_level/models.py - Sales locations → Production locations: references location
velos/high_level/models.py - Sales locations → Stock quantities: references stock
velos/high_level/models.py - Customer invoices → Sales locations: references sales location
velos/high_level/models.py - Customer invoices → Stock quantities: references quantities
velos/high_level/models.py - Django settings → SQLite database: configures database
velos/velos/settings.py - ASGI entrypoint → Django settings: selects settings
velos/velos/asgi.py - WSGI entrypoint → Django settings: selects settings
velos/velos/wsgi.py - Country and city → SQLite database: persists through ORM
- Production locations → SQLite database: persists through ORM
- Machines and quantities → SQLite database: persists through ORM
- Production operations → SQLite database: persists through ORM
- Products and pricing → SQLite database: persists through ORM
- Suppliers and transport → SQLite database: persists through ORM
- Stock quantities → SQLite database: persists through ORM
- Sales locations → SQLite database: persists through ORM
- Customer invoices → SQLite database: persists through ORM