How ahmadghani27/galleryfoto works
Identifikasi Tipe & Tujuan Proyek
• Proyek ini adalah *full-stack web application* monolitik berbasis Laravel (MVC) dengan frontend Blade + Tailwind CSS, backend Laravel + Laravel Breeze untuk Auth, dan MySQL sebagai database.
• Fungsinya untuk CRUD foto & folder, upload massal, operasi massal, favorit, arsip dengan kata sandi, serta manajemen pengguna.
Analisis Struktur File
• Top-level:
• app/ – kode inti (Models, Controllers, Middleware, View Components)
• config/ – konfigurasi aplikasi (DB, Mail, Queue, dsb.)
• database/ – migrations, factories, seeders
• public/ – entry-point index.php, asset (CSS/JS build output)
• resources/ – Blade views, CSS/JS sumber, komponen UI
• routes/ – definisi route (web.php, auth.php)
• storage/ – penyimpanan file upload & cache/sessions
• tests/ – automated tests (Feature & Unit)
• artisan, composer.json, vite.config.js, dsb.
Insight dari README
• Penggunaan Laravel Breeze (Auth), Tailwind CSS, Vite untuk build frontend.
• Database MySQL ‘galeri’ (tabel users, folders, photos, archives).
• Relasi: User→Photos (1-M), Folder→Photos (1-M), Photo→Archive (1-1).
• Fitur utama: upload massal, hapus massal, favorit, pencarian, arsip.
a. Client/Browser
• Mengakses tampilan via HTTPS, mengirim form request (upload, CRUD, auth).
b. Web Server / Application Server
• Nginx/Apache → public/index.php → Laravel HTTP Kernel → Middleware → Controller
c. MVC Layers
• Controllers (AccountController, PhotoController, dst.)
• Models (User, Photo, Folder, Archive)
• Views (Blade templates di resources/views)
d. Database
• MySQL (tabel users, folders, photos, archives)
e. File Storage
• storage/app/public untuk foto, storage/app/private untuk file arsip jika perlu
f. Cache/Session
• File/session cache di storage/framework
g. External Services
• SMTP/Email (EmailVerificationNotificationController)
• Optional: Queue Worker jika queue dipakai
Interaksi & Alur Data
• Client → (HTTPS) → Web Server → Laravel Router → Controller
• Controller ↔ Model → Query ke MySQL
• Controller ↔ FileSystem (upload/download foto)
• Controller → View → HTML/CSS/JS dikembalikan ke Client
• Auth flow: laravel-breeze middleware → RegisteredUserController → Session
Pola Arsitektur & Prinsip
• MVC monolith
• Separation of Concerns: Auth, Photo Management, Folder Management
• RESTful Controllers untuk CRUD
• Blade Components untuk reusable UI
• Configuration via .env & config/*.php
• Testing: PHPUnit/Pest
• Panah Berarah menunjukkan alur request dan data flow (misalnya: Browser → Controller, Controller → Database).
• Kotak biru untuk Application Server
• Silinder hijau untuk Database
• Keterangan Singkat di dekat panah jika perlu (e.g., “POST /photos”, “SELECT * FROM photos WHERE …”).
[Browser]
↓ HTTPS
[Nginx/Apache]
↓
[Laravel App (index.php → Kernel)]
├─ [Middleware (Auth)]
├─ [Controllers] → [Models] → [MySQL DB]
├─ [Controllers] → [Storage (File System)]
└─ [Views (Blade) + Tailwind/Vite JS]
↓
[Response HTML/CSS/JS]
↓
[Browser]