How pablodeleon092/plandecarrera works
Project type and purpose
• This is a full-stack web application built on Laravel (PHP) with Inertia.js and React for the frontend.
• Purpose: manage academic entities (Carreras, Materias, Comisiones, Docentes, Usuarios) via CRUD interfaces, authentication/authorization, and background tasks (queues, jobs).
File structure
• Top-level:
• Dockerfile, docker-compose.yml, nginx config → containerized deployment
• public/index.php → entrypoint
• app/Http/Controllers, Models, Policies → MVC backend
• resources/js/{Components,Pages,Layouts} → React/Inertia UI
• routes/web.php, routes/auth.php → HTTP routing
• database/migrations & seeders → schema + initial data
• config/, bootstrap/, storage/, tests/ → config, bootstrap, persistence, testing
• Architectural patterns:
• MVC on server side (Controllers ↔ Models ↔ Views via Inertia)
• Component-based reusable React UI
• Inertia bridges server and client without an API layer
• Queues for background jobs (config/queue.php)
README
• On the left, “Client (Browser / Inertia + React)” with UI components.
• In the middle, “Server (Nginx → PHP-FPM / Laravel)” with layers: Routing → Controllers → Models → DB.
• On the right, “Persistence & Services” (Database, Redis, File Storage, Mail).
• API boundaries: even though Inertia isn’t a JSON API, illustrate prop-based data flow.
• If Dockerized, show “Docker Compose” umbrella containing App and DB containers.
Elements
– Clear component labels (e.g., “Inertia.js Adapter,” “Eloquent Models,” “Queue Worker”)
• Green for backend services
• Orange for data stores
• Gray for infrastructure (Docker, Nginx)