// the find
JoelleCastelli/DriveNCook
Web application for a food truck company with Laravel 5.5. Admin interface: management of employees, trucks, warehouses, orders and customers. Customer interface: selection of trucks available on a Google Map, payment simulation via Stripe and emailing of a PDF invoice.
A student project — a Laravel 5.5 food truck management system with three user roles (corporate admin, franchisee, customer), Google Maps truck selection, Stripe payment simulation, and PDF invoicing. The interesting part is the companion C programs: a QR code reader pipeline that decodes PNGs via quirc, hits a database, and a GTK subscription client that generates QR codes via libcurl. Two completely separate stacks glued together by a shared MySQL database.
The C QR code subsystem is more substantial than typical student projects — it uses quirc for decoding, lodepng for PNG handling, and has a file listener daemon plus a client subscriber with a GTK UI, which shows real systems thinking. The Laravel side has proper role separation with distinct middleware guards (AuthCorporate, AuthFranchise, AuthClient) rather than a single user table with a role column. The repo includes actual wireframes, ER diagrams, Gantt charts, security audit docs, and network configs (EVE-NG router configs for simulating warehouse VLANs) — this was a serious school project with real documentation discipline.
Laravel 5.5 hit end-of-life in 2018, so this is frozen on a framework version with known unpatched CVEs — not something you'd run in production or learn modern Laravel patterns from. The C components vendor binary blobs directly into the repo (compiled .so files, curl binary) instead of using package managers or build dependencies, which is a red flag for supply chain hygiene. The `key.txt` file sitting next to `key.txte` in the QR subscription client directory suggests secrets may have ended up committed at some point. No tests anywhere in the codebase.