How t0ff1xs/teambog works
Lanay is a restaurant operations and ordering system with PHP APIs backed by MariaDB and browser-based staff and customer screens. Staff sign in, create table orders or receive customer QR orders, and send them into kitchen status handling; waiters mark ready orders served, after which cashiers record payment. Owners manage menus, staff, stock, recipes, and table QR codes. The graph includes documented but prototype-only screens as screens, not as connected backend workflows. Source excerpts show backend calls and persistence; screen-to-API links follow README documentation.
Main entry points: bootstrap.php API foundation · screens Staff work screens · orders.php Order API · owner Owner screens
Components 22
Restaurant screens
- Staff sign-in
screens/sign-in/roles.html - Staff work screens
screens - Customer screens
screens/customer - Owner screens
screens/owner
Ordering and service
- Order API
api/orders.php - Order status API
api/orders/status.php - Customer order API
api/customer-order.php - Order tracking API
api/customer-order-status.php - Payments API
api/payments.php
Management APIs
- Menu API
api/menu.php - Menu data
api/menu_data.php - Inventory API
api/inventory.php - Inventory quantities
api/inventory_helpers.php - Staff API
api/staff.php - Tables API
api/tables.php - Table QR API
api/table-qr.php
Shared backend
- Login API
api/auth/login.php - Session API
api/auth/session.php - API foundation
api/bootstrap.php
Other components
- Staff
- Customer
- MariaDB
Connections 34
- Staff → Staff sign-in: signs in
README.md - Staff sign-in → Login API: submits PIN
README.md - Login API → API foundation: uses
api/auth/login.php - Staff → Staff work screens: uses
README.md - Staff work screens → Order API: creates orders
README.md - Staff work screens → Order status API: updates status
README.md - Staff work screens → Payments API: records payment
README.md - Customer → Customer screens: orders
README.md - Customer screens → Customer order API: loads menu
README.md - Customer screens → Order API: submits order
README.md - Customer screens → Order tracking API: tracks order
README.md - Order API → Inventory quantities: converts quantities
api/orders.php - Inventory API → Inventory quantities: uses
api/inventory.php - Customer order API → Menu data: loads menu
api/customer-order.php - Menu API → Menu data: loads menu
api/menu.php - Owner screens → Menu API: manages menu
README.md - Owner screens → Inventory API: manages stock
README.md - Owner screens → Staff API: manages staff
README.md - Owner screens → Table QR API: manages QR codes
README.md - Staff work screens → Tables API: reads tables
README.md - Session API → API foundation: uses
api/auth/session.php - Order API → API foundation: uses
api/orders.php - Order status API → API foundation: uses
api/orders/status.php - Payments API → API foundation: uses
api/payments.php - Inventory API → API foundation: uses
api/inventory.php - Staff API → API foundation: uses
api/staff.php - Tables API → API foundation: uses
api/tables.php - Table QR API → API foundation: uses
api/table-qr.php - API foundation → MariaDB: connects to
api/bootstrap.php - Order API → MariaDB: reads and writes
api/orders.php - Order status API → MariaDB: updates orders
api/orders/status.php - Inventory API → MariaDB: reads and writes
api/inventory.php - Menu data → MariaDB: reads menu
api/menu_data.php - Payments API → MariaDB: records payments
api/payments.php