amilcar1129/agrosmart2.0-backend

Purpose and entry point

This is a Node.js backend organized as an MVC-style API for public, authentication, administration, community, and survey workflows. The process starts at server.js, which mounts route groups and connects request handling to controllers.

HTTP/API boundary

Route modules divide the API by functional domain:

• Authentication: routes/auth.routes.js

• Administrative operations: routes/admin.routes.js

• Community operations: routes/community.routes.js

• Public-facing access: routes/public.routes.js

• Survey capture/querying: routes/survey.routes.js

Requests flow from these route definitions into their paired controllers rather than directly accessing persistence.

Application control layer

Controllers implement domain-oriented request orchestration, validation/response behavior, and model access:

• controllers/auth.controller.js

• controllers/admin.controller.js

• controllers/community.controller.js

• controllers/public.controller.js

• controllers/survey.controller.js

The main control boundary is route → controller → model/database. Controller separation suggests public reads, privileged administration, community management, and survey handling have distinct API policies.

Authentication and authorization

Authentication logic is centralized in controllers/auth.controller.js, while protected-route enforcement is separated into middleware/auth.js. Password hashing is isolated in hash-password.js.

This creates an important security boundary: authentication establishes user identity, and route middleware should gate administrative or otherwise restricted controller actions before model access.

Domain and persistence model

The persistence layer is collected through models/index.js and contains entities for users, communities, households/families, surveys, socioeconomic records, crops, and animals:

• models/usuario.model.js, models/comunidad.model.js, models/familia.model.js

• models/encuesta.model.js, models/socioeconomico.model.js

• models/cultivo.model.js, models/animal.model.js

These models likely represent the core data graph: users administer or participate in communities; families have survey and socioeconomic records; agricultural and animal records supplement household/community survey data.

Database and uploads infrastructure

Database connection/configuration is isolated at config/database.js, keeping persistence infrastructure outside request handlers. File-upload handling is configured separately for general uploads and gallery-oriented uploads:

• config/multer.js

• config/multer-gallery.js

Multer is the material upload integration implied by these modules. Upload parsing/storage is therefore an infrastructure boundary that controllers or routes can invoke before persisting associated domain records.

Primary flow

A typical request enters server.js, matches a domain router, passes through middleware/auth.js when restricted, optionally uses Multer upload configuration, then reaches a controller. The controller coordinates the relevant models via models/index.js and returns an HTTP response. Database configuration remains behind config/database.js, while password handling remains behind hash-password.js.