How tams-maker/product-inventory-system works
This is a small Flask product-catalog app. A user opens the catalog or search page, then can retrieve products (optionally by name) and add, update, or delete them through the product API; the API persists product records in SQLite. The templates are present, but their client-side behavior was not sampled, so no template-to-API wiring is asserted. The database relationship follows the ORM queries and session writes in db.py.
Main entry points: db.py Page routes · index.html Catalog page · search.html Search page · products.db Products SQLite
Components 7
Web pages
- Page routes
db.py - Catalog page
templates/index.html - Search page
templates/search.html
Product API
- Product API
db.py
Product data
- Product model
db.py - Products SQLite
instance/products.db
Other components
- User
Connections 6
- User → Page routes: requests pages
- Page routes → Catalog page: renders
- Page routes → Search page: renders
- User → Product API: calls API
- Product API → Product model: queries and updates
- Product model → Products SQLite: reads and writes