How emmanrubillos/catering_system works
This is a Laravel catering and event-booking application. Customers browse catering services, menus, inclusions, and events, then configure a reservation with event details, location, guest/package choices, and payment information; submitted bookings are stored as pending and trigger email. Customers can also view reservations and request cancellation or rescheduling, while administrators manage catalogues, users, and reservation status and notifications. The tree and excerpts support these principal areas, but unsampled route declarations and several controllers limit certainty about their exact wiring.
Main entry points: web.php Web routes · MakeReservationController.php Reservation setup · HomeController.php Home catalogue · ServiceController.php Service management
Components 23
Customer booking
- Home catalogue
app/Http/Controllers/Pages/HomeController.php - Reservation setup
app/Http/Controllers/Customer/MakeReservationController.php - Customer profile
app/Http/Controllers/Admin/ProfileController.php - Customer registration
app/Http/Controllers/Auth/RegisterController.php - Booking screens
resources/views/layouts/customer/make_reservation/index.blade.php - Profile screens
resources/views/layouts/customer/profile/index.blade.php
Administration
- Reservation operations
app/Http/Controllers/ReservationController.php - Service management
app/Http/Controllers/Admin/Services/ServiceController.php - User management
app/Http/Controllers/Admin/UserController/UsersController.php - Admin screens
resources/views/admin2
Catering domain
- Services
app/Models/Service.php - Inclusions
app/Models/Inclusion.php - Classifications
app/Models/Classification.php - Events
app/Models/Event.php - Reservations
app/Models/Reservation.php - Users and roles
app/Models/User.php
Web and messaging
- Web routes
routes/web.php - Route provider
app/Providers/RouteServiceProvider.php - Reservation mail
app/Mail/ReservationBookingMail.php - Mail service
Other components
- Customer
- Administrator
- SQL database
Connections 42
- Route provider → Web routes: loads routes
- Customer → Web routes: requests pages
- Administrator → Web routes: requests admin
- Web routes → Home catalogue: dispatches
- Web routes → Reservation setup: dispatches
- Web routes → Customer profile: dispatches
- Web routes → Reservation operations: dispatches
- Web routes → Service management: dispatches
- Web routes → User management: dispatches
- Web routes → Customer registration: dispatches
- Home catalogue → Services: reads catalogue
- Home catalogue → Classifications: reads groups
- Home catalogue → Inclusions: reads inclusions
- Home catalogue → Events: reads events
- Home catalogue → Booking screens: renders
- Reservation setup → Services: reads services
- Reservation setup → Classifications: reads groups
- Reservation setup → Inclusions: reads inclusions
- Reservation setup → Events: reads events
- Reservation setup → Booking screens: renders
- Reservation setup → Reservations: creates booking
- Reservation setup → Reservation mail: sends booking mail
- Reservation mail → Mail service: uses
- Customer profile → Reservations: reads reservations
- Customer profile → Events: reads events
- Customer profile → Profile screens: renders
- Reservation operations → Reservations: updates status
- Reservation operations → Mail service: sends notices
- Service management → Services: manages services
- Service management → Classifications: reads groups
- Service management → Inclusions: reads inclusions
- Service management → Admin screens: renders
- User management → Users and roles: manages users
- User management → Admin screens: renders
- Customer registration → Users and roles: creates account
- Customer registration → SQL database: persists account
- Services → SQL database: reads and writes
- Inclusions → SQL database: reads and writes
- Classifications → SQL database: reads and writes
- Events → SQL database: reads and writes
- Reservations → SQL database: reads and writes
- Users and roles → SQL database: reads and writes