How marcosdavi-dev/memories works
This is a small Express/Mongoose backend for managing memories with images. A client sends requests to the mounted memory API; route handlers apply upload middleware where needed and dispatch operations to the controller, which validates requests, reads or updates memory records, and returns JSON responses. Image uploads are saved under the public directory, while MongoDB stores memory metadata, favorites, and comments. The source excerpts show server wiring and these core operations; no README documents additional product capabilities.
Main entry points: MemoryController.js Memory operations · routes.js Memory routes · app.js Express app · images Public images
Components 9
Server
- Express app
backend/app.js
Memory API
- Memory routes
backend/routes.js - Image upload
backend/helpers/upload.js - Memory operations
backend/controllers/MemoryController.js
Persistence
- Memory schema
backend/models/Memory.js - Mongo connection
backend/db/conn.js - Public images
backend/public/images
Other components
- API client
- MongoDB
Connections 11
- API client → Memory routes: sends requests
backend/routes.js - Express app → Memory routes: mounts at /memories
backend/app.js - Express app → Mongo connection: initializes connection
backend/app.js - Memory routes → Image upload: applies middleware
backend/routes.js - Memory routes → Memory operations: dispatches operations
backend/routes.js - Memory operations → Memory schema: queries and saves
backend/controllers/MemoryController.js - Mongo connection → MongoDB: connects to
backend/db/conn.js - Image upload → Public images: writes uploads
backend/helpers/upload.js - Memory operations → Public images: deletes old images
backend/controllers/MemoryController.js - Express app → Public images: serves static files
backend/app.js - Memory operations → API client: returns JSON
backend/controllers/MemoryController.js