How jeffersongoncalves/filakit works
Project Type and Purpose
• This is a full-stack Laravel 12.x + Filament 3.x starter kit.
• It delivers a monolithic MVC web application with three pre-configured panels:
• Admin Panel at /admin (Admin guard)
• App Panel at /app (User guard)
• Public Panel at / (visitor-facing frontend)
File Structure
• Top-level directories:
• app/ contains Models, Observers, HTTP Middleware, Filament Resources & Pages, Service Providers
• config/filakit.php centralizes panel routes, middleware, branding
• resources/ and public/ hold CSS/JS (Tailwind, Vite, PNPM) and Blade views
• database/ has migrations, seeders, factories
• docker-compose.yml and Sail support containerized MySQL, Redis, Mailpit
• routes/web.php and routes/console.php define HTTP & CLI entry points
• Key patterns: MVC, multi-guard authentication, event observers, queue/job pipeline
Extract Insights from README
• Three panels configured via Service Providers under app/Providers/Filament/
• Multi-guard auth with Admin and User models
• Asset pipeline driven by Vite/PNPM and Tailwind
• Optional Docker/Sail environment for MySQL, Redis, Mailpit
Main Components & Their Relationships
A. Presentation Layer
• Clients: Admin User, Authenticated App User, Public Visitor
• HTTP(S) → Nginx/Apache or Artisan serve → Laravel front controller (public/index.php)
• Vite dev server (PNPM) for live-reloading assets in development
B. Application Layer
• Laravel Router & Middleware (including ProtectFromImpersonation, auth guards)
• Service Providers (AdminPanelProvider, AppPanelProvider, PublicPanelProvider) initialize Filament panels
• Filament Resources & Pages (CRUD UIs for Admins/Users)
• Controllers / Livewire components for dynamic UIs
• Event System & Observers (AdminObserver, UserObserver)
• Queue Workers (via Redis) for background jobs
C. Data Layer
• Primary RDBMS: MySQL (managed by Laravel’s Eloquent)
• Cache & Queue store: Redis
• File Storage: local disk (or S3 if extended)
• Mail Transport: Mailpit or SMTP
D. Infrastructure / DevOps
• Docker Compose (MySQL, Redis, Mailpit, Laravel Sail)
• CI/CD Workflows (.github/workflows) for code style, static analysis, changelog updates
• Environment config via .env and config/*.php
Architectural Patterns & Design Principles
• MVC: clear separation between Models, Views (Blade/Livewire), Controllers/Pages
• Provider-based modularity: each panel is a self-contained module
• Multi-guard authentication and authorization
• Event-Driven: Observers respond to model events
• Dependency Injection & Service Container
• Single monolith with logical modules rather than microservices