How immanuelpartogi/ta-kel-13 works
Project type and purpose
• This is a full-stack ferry-booking system composed of three main applications:
• Backend API (Laravel 11 + MySQL + Redis queues + Midtrans payment integration)
• Mobile client (Flutter multi-platform app for end users)
• Admin panel (React + Vite + Tailwind CSS web application for system management)
• The README confirms a REST-based architecture serving both the mobile app and the admin UI, with additional services for notifications and payments.
File structure
• ferry_booking_system/ (backend)
• app/ (Controllers → Services → Models → Jobs)
• database/ (migrations, seeders)
• config/, routes/, resources/views (Laravel MVC)
• Uses Redis (queues), MySQL, external Midtrans service
• ferry_booking_app/ (mobile)
• lib/api (HTTP clients), lib/services (business logic), lib/providers (state management), lib/models
• Cross-platform code under android/, ios/, web/, linux/, macos/, windows/
• Uses Dio for HTTP, Provider/Bloc for state, Hive/SharedPreferences for local storage, FCM for push
• ferry_booking_management_system/ (admin)
• src/components, pages, services (API wrappers), contexts (AuthContext), hooks (useSettings)
• Vite + React Router + Tailwind + Axios for HTTP
README for additional insights
• Integration with Midtrans for payments, Redis + Laravel Queues for notifications
• JWT authentication, AES-256 encryption on sensitive data, push notifications via FCM
Detail level
• Scheduled jobs invoking Artisan Commands (e.g., CheckPendingPayments, SendBoardingReminders) interacting with Services/Models
• Inside mobile app, illustrate layers: UI Screens → Providers → API clients → local storage