How patrix14r/ramen-master-db works
This repository implements a ramen restaurant storefront with customer accounts, menu browsing, cart and checkout, and order submission. The visible workflow is customer interaction with the browser UI, account verification through the auth API, then checkout and order persistence through the orders API. Menu data is also exposed by a separate products API, but the available excerpts do not show the browser calling it. The SQL schema and connection code indicate MySQL storage; relationships are limited to calls and queries visible in the excerpts.
Main entry points: conexion.php DB Connection · script.js Browser UI · api_auth.php Account API · api_pedidos.php Orders API
Components 10
Storefront
- Storefront Pages
index.html - Browser UI
js/script.js - Products API
api/api_productos.php
Customer Accounts
- Account API
api/api_auth.php - Login Session
api/api_auth.php
Ordering
- Cart and Checkout
js/script.js - Orders API
api/api_pedidos.php
Backend Data
- DB Connection
api/conexion.php - Ramen Database
database/ramen_master_db.sql
Other components
- Customer
Connections 9
- Customer → Browser UI: uses
js/script.js - Browser UI → Account API: requests auth
js/script.js - Account API → Login Session: sets session
api/api_auth.php - Account API → DB Connection: queries
api/api_auth.php - Browser UI → Cart and Checkout: manages cart
js/script.js - Cart and Checkout → Orders API: submits order
js/script.js - Orders API → DB Connection: writes order
api/api_pedidos.php - Products API → DB Connection: queries products
api/api_productos.php - DB Connection → Ramen Database: connects to
api/conexion.php