How conovatec/observatorio-back works
Project Type & Purpose
• This is a monolithic, full-stack Laravel application exposing
• A server-rendered admin/UI layer (Blade + Livewire + Tailwind CSS + Alpine.js)
• A versioned JSON REST API (routes under /api/v1)
• Core features: CRUD on multiple domain entities (posts, categories, youth policies, etc.), user authentication/authorization (Laravel Fortify, Jetstream, Sanctum), pagination, filtering, sorting.
File Structure & Architectural Patterns
• MVC layers in app/: Models (Eloquent), Controllers (app/Http/Controllers), Views/Livewire components (resources/views + app/Http/Livewire).
• API layer under app/Http/Controllers/Api/V1 + Resources in app/Http/Resources/Api/V1.
• Request validation in app/Http/Requests/admin, custom Actions in app/Actions (Fortify & Jetstream hooks).
• Service providers (app/Providers) bootstrap framework features (Auth, Fortify, Jetstream).
• Database migrations/factories/seeders under database/.
• Docker+docker-compose for containerized PHP-FPM, webserver, DB.
Key Components
a. Clients & Interfaces (Presentation Layer)
• Browser/Admin User → Web UI (Blade + Livewire + Alpine.js)
• External Consumer (e.g., mobile app, Postman) → JSON REST API
b. Web & App Servers (Application Layer)
• Nginx/Apache container (docker)
• PHP-FPM container hosting Laravel
• Laravel middleware stack (routing, authentication, localization, CSRF)
• Controller + Livewire component handlers
• Fortify/Sanctum auth services
c. Data & Integrations (Data Layer)
• Primary database (MySQL/PostgreSQL)
• Filesystem storage for uploads (public/storage)
• Optional cache/queue (Redis, if configured)
• External SMTP/mail service
d. Supporting Services
• Laravel’s queue worker (supervisord in Docker)
• Scheduler (cron via docker start-container script)
Relationships & Data Flows
• Web UI flow:
Browser —(HTTP)→ Nginx → Laravel Router → Controller / Livewire → Eloquent Model → Database
←– JSON or HTML response
• REST API flow:
API Client —(HTTP JSON)→ Nginx → Laravel Router (/api/v1) → API Controller → Resource Transformer → Model → Database
←– JSON response
• Authentication:
Login/Register endpoints (Fortify) → Issues Sanctum tokens / session cookies → Middleware guards follow-on requests
• Storage:
File uploads → Laravel Storage → local disk or cloud driver
• Queue/Scheduler:
Dispatch jobs from controllers/actions → Queue worker → Job handlers → possible events/notifications