How bquochuy1514/sportiverse_backend works
Project type and purpose
• This is a Laravel-based headless e-commerce API. There is no monolithic “blade” frontend in the repo; instead you expose JSON endpoints (in routes/api.php) for products, categories, carts, coupons, sports, users and auth. SocialiteController hints at social login.
File structure
• Top‐level “app” directory contains your HTTP controllers (app/Http/Controllers/Api/*), middleware, models, policies and service providers.
• “routes/api.php” defines your REST endpoints.
• “database” holds migrations & seeders for users, categories, products, cart, coupons, etc.
• “config/*.php” files configure database, cache, session, queue, services (Socialite), Sanctum, etc.
• “public/index.php” is your API entry point.
• “storage” + “bootstrap/cache” handle caches, compiled views, logs, sessions, and file uploads.
• You have queue infrastructure (jobs table migration + queue.php config) and filesystem abstraction.
Final guidance
• Be exhaustive: include every model, service, and external dependency.
• How middleware and policies guard your endpoints.
• Async boundaries (where you hand off work to the queue).