How kiruiian/platter works
This is a Flask restaurant meal-management application. Staff log in, then use the menu and table screens; the sampled code supports authenticated menu viewing and administrator menu/table maintenance. The data model also defines orders, order lines, and payments, but the relevant handlers are omitted, so their operational flow is not shown. The database is configured for PostgreSQL; only the supplied source excerpt was inspected.
Main entry points: app.py SQLAlchemy models · login.html Login screen · menu.html Menu screen · tables.html Tables screen
Components 14
Staff access
- Flask application
app.py - Login and roles
app.py - Login screen
templates/login.html - Dashboard screen
templates/dashboard.html
Restaurant operations
- Menu management
app.py - Menu screen
templates/menu.html - Table management
app.py - Tables screen
templates/tables.html - Meal order records
app.py - Payment records
app.py - Order totals
app.py
Persistence
- SQLAlchemy models
app.py - PostgreSQL database
Other components
- Staff
Connections 14
- Staff → Flask application: sends requests
- Flask application → Login and roles: dispatches login
- Login and roles → PostgreSQL database: checks user
- Login and roles → Login screen: renders
- Flask application → Menu management: dispatches menu
- Menu management → PostgreSQL database: reads and writes
- Menu management → Menu screen: renders
- Flask application → Table management: dispatches tables
- Table management → PostgreSQL database: reads and writes
- Table management → Tables screen: renders
- SQLAlchemy models → PostgreSQL database: defines schema
- SQLAlchemy models → Meal order records: models
- SQLAlchemy models → Payment records: models
- SQLAlchemy models → Order totals: stores totals