How salaheddinedaghri/hotel-app-project works
Project Type and Purpose
• This is a monolithic full-stack web application built on Laravel (PHP MVC).
• Purpose: an online hotel room booking system with two user roles (Admin & Customer). Admins manage rooms, users, statuses, payments, transactions. Customers browse rooms, book online, view history, manage profile.
File Structure
• Top-level Laravel scaffolding: artisan, bootstrap/, config/, public/, resources/, routes/, storage/, tests/.
• app/ contains MVC layers:
• Http/Controllers → all HTTP entry points (DashboardController, RoomController, StripeController, etc.)
• Models → Eloquent ORM models (Room, Payment, Transaction, User, etc.)
• Events & Notifications → real-time events (NewReservationEvent, RefreshDashboardEvent) and notification classes
• Console & Providers → artisan commands, service registration, event wiring
• resources/views → Blade templates for admin/dashboard and public frontend
• public/ → static assets (CSS/JS frameworks, custom frontend, invoice templates)
• config/queue, broadcasting, services → hints at using queues (Redis or database) and external services (Stripe, Mail, broadcasting driver)
• database/migrations & seeders → MySQL schema and seed data for rooms, types, users, transactions
README for Additional Insights
• Two distinct user flows: Admin Dashboard (manage back end) vs. Public Booking Site (browse & reserve).
• Real-time updates: reservation events broadcast to dashboard.
• Stripe integration for payment processing.
• Offline reservations sync into the same pipeline.