How hasnayeen/booked works
Project type and purpose
• This is a monolithic, full-stack web application built on Laravel (PHP).
• It provides a bus-booking system (“Booked”) with three user panels: Admin, Operator, and Guest. Operators manage buses, routes, schedules, and bookings; Admin oversees operators and roles; Guests can search and view available routes.
File structure
• Top-level folders:
• public – web root serving index.php, static assets (CSS, JS, fonts).
• app – core application code (Models, Controllers, Policies, Notifications, Filament resources for panels).
• resources – Blade views, localized text, CSS/JS sources.
• routes – web.php and console.php define HTTP and CLI entry points.
• database – migrations, seeders, factories.
• config – Laravel configuration for auth, database, cache, queue, services.
• Filament panels under app/Filament: separate namespaces for Admin, Operator, and Guest.
• Middleware, Requests, Policies enforce business rules and access control.
• Queued notifications and jobs indicated by Notifications and queue.php config.
README
• Minimal description, but “Booked” name implies a booking system.
• No pre-drawn architecture, so we infer patterns from code and directory layout.
Main components
A. Clients
• Admin user interface (Filament AdminPanel)
• Operator user interface (Filament OperatorPanel)
• Guest user interface (Filament GuestPanel + public pages)
B. Web Tier
• HTTP server (Nginx/Apache) + PHP-FPM
• Laravel HTTP Kernel
• Routing layer (routes/web.php)
• Middleware (PanelCommonConfig, auth checks)
• Controllers (app/Http/Controllers)
• Form Requests (validation)
C. Application / Business Logic
• Filament Resource classes (app/Filament/…/Resources)
• Services: Notifications, Policies, Casts, Enums, ValueObjects
• Eloquent Models (Booking, Bus, Route, RouteSchedule, User, Operator, Role, Permission)
D. Data Layer
• Relational Database (MySQL/PostgreSQL) – tables created via migrations under database/migrations
• Eloquent ORM for read/write operations
E. Infrastructure Services
• File Storage (local / S3) for logo and uploaded assets
• Queue system (Redis / database) for asynchronous jobs (notifications)
• Mail / Notification service (SMTP, Mailgun, etc.)
• Cache (file or Redis)
F. Development / CI
• GitHub Actions (lint.yml, tests.yml)
• PHPUnit / Pest tests (tests/Feature, tests/ArchTest.php)
• Vite for front-end asset bundling
Relationships and interactions
• Browser (Admin/Operator/Guest) → HTTP request → Web server → Laravel Kernel → Route → Middleware → Controller / Filament Resource → Eloquent → Database
• File uploads/downloads handled within Storage facade → file system or S3
• Notifications dispatched via Laravel’s queue → Queue worker → Mail / database notifications
• Auth and RBAC enforced by Policies and app/Models/Role & Permission
Architectural patterns & principles
• Layered architecture: Presentation (Blade, Filament UI), Application (Controllers, Filament Resources), Domain (Models, ValueObjects, Enums), Infrastructure (DB, Storage, Mail, Queue).
• MVC at core, extended by Filament for CRU(D) admin panels.
• Role-based access control via Policies, Permissions, Middleware.
• Dependency injection via Service Providers (app/Providers).
• Single codebase multi-panel design by namespacing Filament resources.