How albertpf/tickets works
Project type and purpose
• This is a monolithic, full-stack Laravel web application (“tickets”) that provides an internal ticketing/support system.
• It exposes two main user interfaces:
• An Admin dashboard (Blade templates under resources/views/admin).
• A public/portal interface (under public/portal).
• Back-end responsibilities include user/auth management, ticket/assignment workflows, activity logs, background jobs, and database migrations/seeders.
File structure
• Top-level directories:
• app/ → Core Laravel MVC code (Controllers, Models, Jobs, Middleware, Exceptions, Helpers)
• resources/views/ → Blade templates, split into admin, auth, layout, and portal index files.
• public/, public/portal → Served assets (CSS/JS/fonts/images) and entry points (index.php, portal main).
• routes/ → web.php, api.php, console.php, channels.php define HTTP/API/CLI routes.
• database/ → Migrations, factories, seeders for tables: users, tickets, soportes, actividades, bitacora, etc.
• config/ → Laravel configuration for auth, database, cache, mail, queue, CORS, sanctum, etc.
• bootstrap/, vendor/ → Framework bootstrap and dependencies.
• Uses Laravel’s MVC pattern and Eloquent ORM, background queue jobs (app/Jobs), middleware stack (app/Http/Middleware), service providers for bootstrapping (app/Providers).