jeanajsja/sgsdev

Purpose and Entry Points

SGSDev is a Python web application for managing users, roles, teachers, rooms, and room reservations. The primary application entry point is backend/main.py; production-style WSGI hosting is exposed through wsgi.py. The browser UI is server-rendered from frontend/templates/login.html and frontend/templates/index.html.

HTTP/Application Boundary

backend/main.py likely composes the web server, template/static serving, and route registration. Controllers form the request-facing boundary for each business area:

• backend/controllers/usuario_controller.py

• backend/controllers/reserva_controller.py

• backend/controllers/salon_controller.py

Requests should enter controllers, which delegate domain work rather than directly owning persistence behavior.

Domain and Authorization Model

The central identity model is users with roles and role-specialized actors. Core entities are represented in:

• backend/models/usuario.py

• backend/models/rol.py

• backend/models/administrador.py

backend/models/docente.py and backend/models/operador.py indicate distinct teacher and operator responsibilities, while administrators are modeled separately. This structure makes role assignment and actor-specific permissions a material boundary around reservation operations.

Reservation Workflow

Reservations are a first-class domain flow connecting users/teachers to rooms. Its layers are:

• backend/controllers/reserva_controller.py

• backend/services/reserva_service.py

• backend/models/reserva.py

The service layer is the likely policy point for creating, querying, updating, or cancelling reservations and for enforcing room availability constraints. It coordinates the reservation model with the room domain rather than exposing database operations directly to controllers.

Room and Teacher Management

Room inventory and teacher records are independently managed, then consumed by reservation workflows:

• backend/services/salon_service.py

• backend/models/salon.py

• backend/services/docente_service.py

Their corresponding controllers, backend/controllers/salon_controller.py and backend/controllers/docente_controller.py, provide the application-facing operations. These domains should remain separate from reservation policy except through service/model interfaces.

Persistence Layer

Database integration is centralized under:

• backend/database/db_config.py

• backend/database/script.sql

script.sql defines the database bootstrap/schema contract; db_config.py is the runtime connection/configuration boundary. Models and services depend on this persistence layer, while controllers should not need database-specific knowledge.

Frontend and Runtime Assets

The frontend is a lightweight template-and-static-asset layer:

• frontend/templates/index.html

• frontend/static/js/dashboard.js

• frontend/static/css/styles.css

The dashboard JavaScript likely drives client-side interactions after login, while server endpoints provide user, room, and reservation data/actions. Python dependencies are defined in requirements.txt, and the selected interpreter version is pinned by .python-version.