How mateobetancurb/bienes-raices-web-site works
Main Components
• Client (Browser): Renders HTML/CSS/JS (views, public/js, public/css)
• Web Server (Express):
– Entry Point: index.js
– Routes: routes/*.js
– Controllers: controllers/*.js
– Middlewares: middlewares/*.js
– Helpers (emails, tokens): helpers/*.js
• Data Layer:
– Models: models/*.js
– DB Connection: config/db.js
– Seeders: seed/*.js
• Static Asset Pipeline: Webpack (webpack.config.js), PostCSS (postcss.config.js), Tailwind (tailwind.config.js)
• File Storage: public/uploads via subirImagen middleware
• External Services: Email service (in helpers/emails.js), token generation (helpers/tokens.js)
Relationships & Interactions
• Browser → HTTP Request → Express Route → Controller → Model → Database → Controller → Response → Browser
• Controllers invoke Helpers (email confirmation, token handling)
• Middlewares handle authentication (identificarUsuario, protegerRuta) and file uploads (subirImagen)
• Static asset requests served directly from public/
• Build pipeline (Webpack/PostCSS) generates assets into public/css and public/js
• Seed scripts populate initial data in the database
Architectural Patterns & Principles
• MVC (Models, Views, Controllers) for clear separation of concerns
• Layered Architecture (Presentation, Application, Data)
• Configuration Management for environment-driven DB connections
• Extensibility via Helpers and Seeders
Relevant Technologies
• Node.js, Express.js
• Pug templating engine
• Tailwind CSS, PostCSS, Webpack
• Relational or NoSQL database (configured in config/db.js)
• Email service integration (helpers/emails.js)
• Authentication & Authorization middlewares
Detailed Coverage
• config/db.js and models/*.js as the Data Model component
• routes/*.js under API Gateway or Router
• Middleware (identificarUsuario, protegerRuta, subirImagen) on the request flow
• Distinguish source JS (src/js) from built JS (public/js)
• Seeder folder (seed/*.js) as an auxiliary data-initialization module