This guide walks you through getting a fully functional local instance of Sistema de Admisión Web running on your machine. The process covers cloning the source code, installing all PHP and JavaScript dependencies, wiring up the environment file, running the database migrations and seeders, and starting the development servers. The whole setup typically takes under ten minutes on a machine that already has the required runtimes installed.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/ariellukezz/admision-web/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites: PHP 8.2 or higher and Node.js 18 or higher are required. You also need Composer, a running MySQL instance (8.0+ recommended), and optionally Redis if you plan to use the cache and queue drivers beyond the defaults. Verify your versions with
php -v and node -v before proceeding.Setup Steps
Install PHP dependencies
Use Composer to install all backend packages declared in
composer.json. This pulls in Laravel 11, Inertia.js server-side adapter, Spatie Permission, Firebase PHP SDK, PDF generation libraries, and all other PHP dependencies.If you are running in a production-like environment, add the
--no-dev --optimize-autoloader flags to skip development-only packages and optimise the Composer autoloader.Install JavaScript dependencies
Install all frontend packages declared in
package.json — including Vue 3, Inertia.js client adapter, Ant Design Vue 4, Tailwind CSS, Vite, Chart.js, Firebase JS SDK, and the rest of the frontend toolchain.Configure the environment
Copy the example environment file to create your local Next, open If you want to enable push notifications during local development, also set the Firebase variables — see the Configuration reference for the full list of available variables.
.env, then generate a unique application encryption key..env in your editor and update the database connection variables to match your local MySQL instance:Run migrations and seeders
Create all database tables and seed the initial RBAC data (modules, views, actions, and permissions) with a single command.The
RbacSeeder populates the rbac_modules, rbac_views, rbac_actions, and rbac_permissions tables. Once complete, you can assign permissions to roles through the Roles y Usuarios module in the admin panel.Start the development servers
The application requires two processes running in parallel: the Laravel PHP development server and the Vite asset bundler with Hot Module Replacement.Open two terminal windows (or use a process manager) and run each command in its own window:Once both servers are running, open http://localhost:8000 in your browser. The login page will load, served by Inertia.js with assets hot-reloaded by Vite.
Dev Server Commands at a Glance
What Happens After Login
After successfully logging in,AuthenticatedSessionController@store inspects the authenticated user’s id_rol and redirects them to their dedicated portal:
| Role | Landing URL |
|---|---|
| Admin (1) | /admin/dashboard |
| Revisor (2) | /revisor |
| Segundas (3) | /segundas |
| Simulacro (6) | /simulacro |
| Calificador (7) | /calificacion |
| Postulante (8) | /postulante/dashboard?seleccionar_proceso=1 |
The first time you log in as Admin, navigate to Roles y Usuarios → Roles to assign RBAC permissions to each role. Roles are seeded without permissions by default — the
RbacSeeder creates the permission matrix but does not bind it to any role automatically.