How danielayala-06/proyecto-final-seminario works
Project type and purpose
• This is a full-stack web application (“Proyecto para gestionar prestamos”) built with Node.js/Express on the back end, serving a server-rendered multi-page UI and client-side JavaScript for dynamic behavior. Its goal is to allow users to create and manage clients, loans (préstamos), and payments (pagos).
File structure
• Top-level server entry: server.js
• Configuration: config/db.js (database connection)
• Routing layer: routes/*Router.js (Express routers for cliente, prestamos, pagos)
• Controller layer: controllers/*Controller.js (business logic for each entity)
• Public (web assets):
• public/views/... (HTML templates organized by feature)
• public/js/*.js (client-side scripts)
• Package and environment: package.json / .gitignore / .vscode
Pattern: a classic MVC (Model-View-Controller) or layered architecture:
• Router → Controller → Database
• Views + JS handle the client side
README
a. Main components
1. Client browser (renders HTML + runs client JS)
2. Web server (Node.js/Express)
• Router layer
• Controller layer
• Database access (via config/db.js)
3. Database (e.g., MySQL / PostgreSQL / MongoDB)
4. Static asset store (public folder)
5. Optional: Development tools (VSCode launch, environment variables)
b. Relationships and interactions
• The client issues HTTP requests (GET/POST) to Express routers.
• Routers forward to controllers.
• Controllers validate input, execute queries via the DB connector in config/db.js.
• Database returns results; controllers format responses.
• Server renders HTML views or returns JSON.
• Client-side JS fetches additional data or posts new data.
c. Architectural patterns and principles
• Layered / MVC: clear separation between routing, business logic, and data access.
• Directory-by-feature organization for views and scripts.
• Single responsibility: each controller handles one entity (cliente, prestamo, pago).
d. Key technologies
• Node.js, Express.js
• Database driver (e.g., mysql2 or mongoose) in config/db.js
• HTML templating (static HTML in public/views)
• Client-side JS for dynamic forms
• package.json for dependencies
Detail
• Important scripts (e.g., pago.js calls /pagos endpoint).
• Which HTML view maps to which router/controller.
• Environment/config dependencies (e.g., .env for DB credentials).