What's in the package
The application, ready to upload as a single file, and this documentation. Nothing to compile, nothing to download separately.
The download at a glance
| Item | What it is |
|---|---|
quickmunch.zip | The complete application. Upload this one file to your host and extract it there — no need to transfer thousands of files. |
Documentation/ | This guide. Open index.html in any browser; it works offline. |
Installation Setup Guide.pdf | A three-page walkthrough of the two setup shapes, for printing or reading first. |
Every dependency ships inside the application folder. You never run
composer install or npm — extract, upload, install.
Inside the application folder
| Path | Holds |
|---|---|
public/ | The web root: front controller, styles, scripts, images and the installer/. Your domain should serve this folder (a bundled rule redirects visitors into it if the domain points one level up). |
public/uploads/ | Every image anybody uploads after install. Ships empty; back it up like a database. |
app/ | Controllers, models and services — the application's logic. |
resources/views/ | Every page template, grouped by area (storefront, vendor, admin, driver…). |
routes/ | URL registrations, one file per area of the product. |
config/, bootstrap/ | Framework configuration and boot files. |
database/ | schema.sql (the tables) and seed.sql (the demo content) the installer imports. |
lang/ | Interface translations (English, Spanish, Arabic) — see Languages. |
storage/ | Logs, caches and generated files. Must be writable; ships empty. |
vendor/ | Bundled PHP dependencies. Ships complete — do not delete or "reinstall". |
.env (created at install) | Your configuration — database credentials and the application key. The installer writes it; treat it like a password. |
tests/ | The automated test suite — run php artisan test after changing code. Not needed to install or operate the site. |
build/ | Asset build scripts for developers who edit the CSS/JS sources. Everything is pre-built; buyers never run these. |
artisan | The command-line entry point, used only for the scheduled-tasks cron line. |
Trying it before you commit
The fastest look is the live demo — the storefront, every dashboard and the demo data are all there, with the one-click role sign-ins below on its login page. Installing locally with demo data (see Local machine setup) gives you the identical experience on your own machine.
Demo accounts
Live demo: https://quickmunch.metropolitanhost.com
Sign in: https://quickmunch.metropolitanhost.com/login
Everyone signs in at the same address — /login. There is no separate
sign-in page per role: the account decides which dashboard opens, and
Lands on below names it. A staff role opens the first page its permissions
allow, so a role you compose yourself gets a working home without one being written
for it.
One-click sign-ins appear on the login page while demo mode is on — that is how the live demo works, and a buyer's own install ships with demo mode off. Sign in with these directly:
| Role | Password | Lands on | |
|---|---|---|---|
| Super admin | admin@example.com | demo1234 | The platform dashboard |
| Restaurant owner | vendor@example.com | demo1234 | The restaurant dashboard |
| Manager | manager@example.com | demo1234 | The restaurant dashboard, manager view |
| Kitchen staff | kitchen@example.com | demo1234 | The kitchen pipeline |
| Host | host@example.com | demo1234 | Tables & reservations |
| Waiter | waiter@example.com | demo1234 | The floor & POS view |
| Customer | customer@example.com | demo1234 | The storefront, signed in |
| Rider | driver@example.com | demo1234 | The delivery app |
Delete these accounts before the site goes live. They all share one password, published here and in every copy of this documentation, so on a public site they are eight working sign-ins that anyone can use. Remove them under Admin → Users, and the sample venues under Admin → Restaurants. Only the administrator you created during installation is yours — nothing you delete there can lock you out.