How aliefauzan/keretaxpress works
Project type and purpose
• This is a full-stack train-booking application named KeretaXpress.
• It comprises:
• A Flutter-based multi-platform mobile/desktop frontend (Android, iOS, Web, Windows, macOS, Linux)
• A Next.js React-based web frontend (in web_version/)
• A Laravel-based RESTful backend API (tesbackend/)
• A MySQL (or compatible) database plus file-storage for uploads
• CI/CD pipelines (GitHub Actions, Cloud Build) and optional Docker containerization
File structure
Top-level directories and their roles:
• frontend/ → Flutter app source (lib/core services, models, screens, widgets; platform folders under android, ios, web, windows, macos, linux)
• tesbackend/ → Laravel API (app/Http/Controllers, app/Models, app/Services; config, database/migrations & seeders; routes/api.php; Dockerfile & docker-compose.yml; CI workflows)
• web_version/ → Next.js web client (src/app pages, components, utils, lib/api.ts; Next.js config files)
README for additional insights
• Business flows: user registration/login → train schedule query → seat selection → booking creation → payment (proof upload → status update) → booking history & filtering
• Key technologies: Flutter, Dart, http, intl, flutter_dotenv; Laravel 10.x, PHP 8.1+, Sanctum/personal-access tokens, MySQL; Docker; GitHub Actions
Elements
• UI clients (e.g., blue rectangles)
• API/server (green rectangle)
• Clear labels on each component (e.g., “Flutter App”, “Laravel API”, “MySQL DB”)
• HTTP requests/responses
• Database read/write
• Event publishing