ramirezlzrga/reforma

Purpose and entry points

This is a Laravel PHP application for collecting user “aportaciones” (contributions) and administering users and submitted contributions. HTTP requests enter through public/index.php, bootstrap via bootstrap/app.php, and are mapped in routes/web.php. CLI maintenance and data-volume operations enter through artisan and app/Console/Commands/.

Web and authentication boundary

Request handling is centered on application, authentication, and administration controllers:

• app/Http/Controllers/AuthController.php

• app/Http/Controllers/AportacionController.php

• app/Http/Controllers/AdminController.php

Authentication-facing screens are server-rendered Blade views under resources/views/auth/. Authorization is separated into middleware, notably app/Http/Middleware/IsAdmin.php, with app/Http/Middleware/PreventBackHistory.php handling browser-history behavior around protected sessions.

Contribution workflow

The primary user workflow is likely authenticated access to a contribution dashboard, creation or management of contribution records, and persistence through Eloquent:

• resources/views/aportacion/dashboard.blade.php

• app/Models/Aportacion.php

• database/migrations/2026_03_17_154008_create_aportaciones_table.php

AportacionController forms the boundary between web input/views and the contribution data model. The database migration is the authoritative schema definition for this domain entity.

Administrative workflow

Administration has a dedicated controller, layout, dashboard, and partial table rendering:

• app/Http/Controllers/AdminController.php

• resources/views/admin/dashboard.blade.php

• resources/views/admin/partials/aportaciones_table.blade.php

The admin UI also includes user-table rendering in resources/views/admin/partials/users_table.blade.php. Admin-specific browser assets are separately published under public/css/admin-style.css and public/js/admin-app.js, indicating a distinct operational interface from the contributor-facing UI.

Persistence and identity

The core persisted entities are users and contributions:

• app/Models/User.php

• app/Models/Aportacion.php

• database/migrations/0001_01_01_000000_create_users_table.php

Laravel auth/session/database behavior is configured through config/auth.php, config/session.php, and config/database.php. Initial privileged and sample identities are seeded through database/seeders/AdminUserSeeder.php and database/seeders/UserSeeder.php. Cache and queue table migrations exist, so deployments may use database-backed cache/queue infrastructure.

Runtime, operations, and assets

The runtime is Laravel/PHP with Composer dependencies (composer.json) and a Vite-based frontend asset pipeline (vite.config.js, package.json). Production web serving is expected to expose public/, including public/.htaccess.

Operational data management is explicitly supported by:

• app/Console/Commands/SeedLargeDataCommand.php

• app/Console/Commands/CleanupLargeDataCommand.php

• database/seeders/DatabaseSeeder.php

These commands suggest the application is intended to handle sizable user/contribution datasets and provides controlled setup and cleanup paths outside normal HTTP flows.