How towhidcse4/sport_app_php works
Project type and purpose
• This is a full-stack, monolithic Laravel application serving both an Admin Panel (Blade + Livewire) and a JSON API (Laravel controllers under app/Http/Controllers/API).
• It is containerized via Docker (Nginx, PHP-FPM, workspace) and likely uses a separate database container or external RDBMS, plus external services for mail and object storage.
High-level file-structure analysis
• Top-level Docker setup (.docker/, docker-compose.yml) defines the runtime containers.
• public/ holds the web entrypoint (index.php), compiled CSS/JS (Tailwind, Mix).
• app/ contains the MVC layers:
• Http/Controllers (API vs Admin vs Auth vs LandingPage)
• Livewire components for reactive UI
• Models, Repositories, Services, Helpers, etc.
• resources/views/ holds Blade templates for Admin, Auth, Landing, Livewire UIs.
• routes/ defines web vs api routes.
• config/ and bootstrap/ hold framework wiring.
• database/ migrations & seeders for schema and initial data.
• tests/ for Feature/Unit tests.
Key architectural patterns & layers
• MVC: Controllers → Views (Blade/Livewire) or JSON Resources → Models → Database.
• Repository pattern (app/Repositories/Eloquent*Repository) abstracts data access.
• Service layer (app/Services/JwtService) for business logic, authentication, third-party integrations.
• Form Requests (app/Http/Requests) validate incoming payloads.
• Middleware (app/Http/Middleware) for auth, CSRF, localization, and gating.
• Docker containers isolate Nginx, PHP-FPM, workspace; docker-compose connects DB & storage.
Main components
a. Client layer
• Browser (Admin UI)
• SPA/JS (resources/js + Livewire)
• Mobile app or external client hitting /api
b. Web server layer
• Nginx container: handles HTTPS, static assets (CSS/JS/images), proxies PHP requests.
c. Application layer
• PHP-FPM container running Laravel
• Laravel HTTP Kernel → Middleware → Controllers (Web & API) → Services & Repositories → Models
• Livewire package for reactive components
d. Data layer
• Relational Database (MySQL/PostgreSQL) container or external service
• Object Storage (OCI Object Storage via OciObjectStorageServiceProvider)
• Mail service (SMTP/Mailgun via Mailer configured in config/mail.php)
• (Optional) Cache & Queue backends (Redis or DB, per config)
e. External integrations
• Third-party auth (social login via config/services)
• Email verification & notifications
• Any external APIs consumed by Services
Relationships & data flow
• Client → HTTPS → Nginx → PHP-FPM → Laravel Router → Controller
• Controller → Service/Repository → Database (CRUD)
• Controller → Resource → JSON (API) or Blade View/Livewire DOM (Web) → HTTP Response → Client
• Laravel Events/Jobs → Queue (if used) → Worker (PHP-FPM) → External services (email, storage)
• Volumes: Workspace container ↔ shared code ↔ PHP-FPM & CLI