How om3027/recidron_backend_proyecto works
Recidron is a FastAPI backend for campus waste reporting and security administration. Users submit and manage waste reports, locations and catalog data; administrators manage accounts, roles, sessions and audit activity. The documented API also provides report statistics and PDF exports, while source excerpts show report-photo uploads. The graph follows the visible request-to-service flow and the documented service/repository layering. Some route and repository implementations were not sampled, so uncertain links are omitted; the README’s SQLite description differs from the sampled MySQL configuration.
Main entry points: repositorios Entity repositories · usuarios.py User routes · servicio_autenticacion.py Authentication service · reportes.py Report routes
Components 23
API and access
- FastAPI application
main.py
Waste reporting
- Report routes
routes/reportes.py - Catalog and geo routes
routes - Statistics routes
routes/stats.py - Report service
servicios/servicio_reportes.py - Catalog service
servicios/servicio_catalogos.py - Geolocation service
servicios/servicio_geolocalizaciones.py - Statistics service
servicios/servicio_estadisticas.py - PDF export
utils/pdf_export.py
Security management
- User routes
routes/usuarios.py - Auth dependencies
routes/auth.py - User service
servicios/servicio_usuarios.py - Authentication service
servicios/servicio_autenticacion.py - Session service
servicios/servicio_sesiones.py - Email delivery
utils/email.py - Password hashing
utils/security.py
Persistence and integrations
- Report repository
repositorios/repositorio_reportes.py - Entity repositories
repositorios - Domain models
models/project.py - Database sessions
models/database.py - Cloudinary storage
utils/cloudinary_upload.py
Other components
- API client
- MySQL database
Connections 29
- API client → FastAPI application: calls API
- FastAPI application → Report routes: registers routes
main.py - FastAPI application → User routes: registers routes
main.py - Report routes → Report service: calls
routes/reportes.py - Report routes → PDF export: generates PDF
routes/reportes.py - Report routes → Auth dependencies: requires permission
routes/reportes.py - User routes → User service: calls
routes/usuarios.py - User routes → Session service: starts login
routes/usuarios.py - User routes → Authentication service: handles recovery
routes/usuarios.py - User routes → Auth dependencies: uses dependencies
routes/usuarios.py - Auth dependencies → Authentication service: validates token
routes/auth.py - Auth dependencies → Entity repositories: checks permission
routes/auth.py - Catalog and geo routes → Catalog service: delegates catalog work
routes/materiales.py - Catalog and geo routes → Geolocation service: delegates location work
- Statistics routes → Statistics service: delegates statistics
- Statistics routes → PDF export: exports PDF
routes/stats.py - Report service → Report repository: uses repository layer
servicios/servicio_reportes.py - Catalog service → Entity repositories: uses repositories
servicios/servicio_catalogos.py - Geolocation service → Entity repositories: uses repositories
servicios/servicio_geolocalizaciones.py - Statistics service → Entity repositories: uses repositories
servicios/servicio_estadisticas.py - User service → Entity repositories: uses repositories
servicios/servicio_usuarios.py - Authentication service → Entity repositories: uses repositories
servicios/servicio_autenticacion.py - Session service → Entity repositories: uses repositories
servicios/servicio_sesiones.py - Report service → Cloudinary storage: uploads photos
servicios/servicio_reportes.py - Authentication service → Email delivery: sends recovery email
servicios/servicio_autenticacion.py - Authentication service → Password hashing: hashes credentials
servicios/servicio_autenticacion.py - User service → Password hashing: hashes passwords
servicios/servicio_usuarios.py - Database sessions → MySQL database: connects to
models/database.py - Domain models → Database sessions: uses ORM base
models/project.py