kevin-garcia27/proyecto-intercambio_servicios_y_habilidades

Purpose and topology

Semackro is a Spanish-language service-exchange platform with a static/vanilla-JS frontend and a Node.js backend. Core domains include user profiles, skills/services, exchange requests and work orders, messaging/video calls, reputation, verification, reporting, and administration.

Entry points

• Backend HTTP server: SemackroBackend/server.js

• Backend package/runtime definition: SemackroBackend/package.json

• Frontend main shell and browser bootstrap: SemackroFrontend/index.html, SemackroFrontend/app.js

• Frontend deployment configuration: SemackroFrontend/vercel.json

Browser application

The frontend is primarily multipage HTML with shared JavaScript rather than a single SPA. Authentication, API invocation, permissions, session handling, and translations are centralized in SemackroFrontend/js/apiHelper.js, SemackroFrontend/js/auth-guard.js, and SemackroFrontend/js/permisos.js. Major user surfaces include discovery, profile, login, exchange requests, reports, and video calling: SemackroFrontend/Descubrir.html, SemackroFrontend/Perfil_Usuario/perfil.html, SemackroFrontend/solicitud_intercambio.html.

API and domain routing

SemackroBackend/server.js composes route modules under SemackroBackend/routes/, forming the backend boundary between browser clients and persistence/services. Identity and access routes are separated from core account/profile APIs: SemackroBackend/routes/Login.js, SemackroBackend/routes/auth.js, SemackroBackend/routes/Personas.js. Profile capability data is handled through SemackroBackend/routes/PerfilCompleto.js and SemackroBackend/routes/HabilidadesYServicios_Persona.js.

Exchange lifecycle and engagement

The central transactional flow likely starts with a service/interchange request, advances into exchanges or work orders, and produces history, ratings, and metrics. Its principal route boundaries are SemackroBackend/routes/SolicitudesIntercambio.js, SemackroBackend/routes/intercambios.js, and SemackroBackend/routes/ordenesTrabajo.js; subsequent quality/reputation paths reside in SemackroBackend/routes/calificaciones.js and SemackroBackend/routes/MetricasDesempeno.js.

Realtime communication and media

Messaging, notifications, call signaling, and video calls are distinct backend capabilities: SemackroBackend/routes/Mensajeria.js, SemackroBackend/routes/call-signals.js, SemackroBackend/routes/videollamadas.js. Shared socket lifecycle is represented by SemackroBackend/socketInstance.js. Uploads and messaging images cross a storage boundary through SemackroBackend/routes/upload.js, SemackroBackend/routes/ImagenesMensajeria.js, and SemackroBackend/cloudflareR2.js; Cloudflare R2 is the evident external object-storage integration.

Security, governance, and operations

Authentication configuration and email integration live in SemackroBackend/config/passport.js and SemackroBackend/config/email.js, with Google auth exposed by SemackroBackend/routes/authGoogle.js. Authorization and audit controls wrap protected operations via SemackroBackend/middlewares/verificarPermiso.js and SemackroBackend/middlewares/auditLogger.js. Administrative governance includes user reports, verification, roles/permissions, and audit logs: SemackroBackend/routes/ReportesUsuarios.js, SemackroBackend/routes/verificacionUsuarios.js, SemackroBackend/routes/bitacora.js.

Persistence and schema evolution

The backend database connection boundary is SemackroBackend/db.js. SQL setup files establish key schema areas—users/companies, roles and permissions, system configuration, pets, and audit records—under SemackroBackend/BaseDatos/, notably setup_final.sql, setup_roles_permisos_motivos.sql, and setup_bitacora.sql. Numerous root-level backend scripts implement direct schema repair, migration, seeding, and operational inspection, indicating database evolution is script-driven rather than managed by a single migration framework.