How estrosebas/sistema-asistencia-integrador works
Project type and purpose
• This is a full-stack web application (“Sistema Asistencia Integrador”) composed of a React/Vite frontend and a Spring Boot backend, containerized via Docker and orchestrated with Docker Compose. Its purpose is to provide user login/registration, attendance marking (including QR generation and scanning), event configuration, attendance history, reporting, and user management.
File structure
• Top level:
• docker-compose.yml, render.yaml – container orchestration definitions
• Base-De-Datos.sql – initial database schema/dumps
• Sistema-asistencia-frontend – React/Vite SPA with its own Dockerfile and nginx.conf
• Sistema-asistencia-backend – Spring Boot service (pom.xml, Dockerfile, Maven wrapper, src & tests)
• Frontend subfolders:
• src/Login, src/Register, src/Home, src/User, src/Manager, src/Admin – React components grouped by UI role
• public & build – static assets and compiled output served by Nginx
• Backend subfolders:
• src/main/java/api/example/apis – Controllers (AuthController, ReporteController), DTOs (LoginRequest/Response, RegisterRequest/Response, SessionResponse), domain objects (Evento, RegistroAsistencia), main class (ApisApplication)
• src/main/resources – application.properties, logging config
• src/test – unit/integration tests with Allure results
README for additional insights
• Lists use cases (login, user registration, attendance creation, marking attendance, QR generation, reporting, history, configuration, user management).
• Emphasizes Docker-based deployment: building frontend & backend containers and bringing them up via docker-compose up --build.
Detail without over-splitting
• Every logical component (UI modules by role, API controllers, DB) but avoid drawing each small React component.
• Integration points: QR-scanner integration in the User Panel, Docker Compose service links.