How osama8809/bus-booking-system works
Project type and purpose
• This is a monolithic, full-stack Laravel application (PHP 8, Laravel Sail/Docker) exposing two JSON APIs for seat-availability and booking plus a Blade-based admin UI.
• Domain: bus fleet management / seat reservation across predefined trips and stations.
File structure
• Top-level folders & files:
• app.php, artisan, console.php – Laravel’s entrypoints
• api.php, web.php – route definitions for JSON APIs vs web/admin UI
• Controllers (e.g., ReservationsController.php, RegisteredUserController.php, VerifyEmailController.php)
• Domain Models & Factories at root: Bus, City, Trip, TripsSeat, Reservations, User + Factories
• config/*.php – all Laravel config files (database, cache, queue, cors, sanctum, etc.)
• docker-compose.yml – orchestrates PHP, MySQL, Node (for front-end builds)
• package.json, vite.config.js, tailwind.config.js, postcss.config.js – front-end asset pipeline
• bus-seats-reservations.mwb – MySQL workbench schema model
README for additional insights
• Two public APIs:
• GET /available-seats?start={station}&end={station}
• POST /reservations (user books a seat)
• Laravel Sanctum for API auth, seeders/migrations to bootstrap trips, buses, cities
• Admin UI at /admin uses Blade templates
a. Main components
• Client layer:
• Web browser (admin UI, Blade + JS assets)
• Mobile/web clients (consume JSON API via /api/* endpoints)
• API Gateway & Web Server:
• Nginx (or Sail’s default) routing incoming HTTP to PHP-FPM
• Application layer (Laravel)
• Routes (api.php vs web.php)
• Controllers (ReservationController, CityController, etc.)
• Services or Domain Logic (business rules for “can I book seat X?”)
• Models / Eloquent Repositories (Bus, City, Trip, TripsSeat, Reservations, User)
• Persistence layer:
• MySQL (database container) with tables for cities, trips, seats, reservations, users
• Infrastructure / DevOps
• Docker Compose orchestrating containers (PHP, MySQL, Node)
• Vite/Tailwind build container for front-end assets
• Scheduler / Queue (if used for notifications)
b. Relationships & interactions
• User → Nginx → Laravel (api.php) → ReservationController → Trip/Seat model → MySQL
• Admin UI: Browser → Nginx → Laravel (web.php) → Blade templates → DB
• Docker Compose: inter-container networking among PHP, DB, Node
• Sanctum issues tokens → used in API calls
c. Architectural patterns & design principles
• MVC (Controllers, Models, Views/JSON responses)
• Layered architecture (Presentation → Application → Domain → Infrastructure)
• Dependency inversion for config/services, use of factories for testing
• Containerization for environment parity (Docker)
d. Key technologies & frameworks
• PHP 8 + Laravel 10 (HTTP Kernel, Service Container, Eloquent ORM, Sanctum)
• MySQL (docker-compose)
• Docker & Laravel Sail
• Vite + Tailwind CSS + PostCSS for front-end assets
• PHPUnit for unit tests