How khievsothy/culture-back-end works
This is a Node/Express cultural-heritage API. Clients call the server’s mounted resource routes; route handlers delegate to controllers that implement account and heritage-resource operations, which use Mongoose models for persistence. Authentication includes password and Google OAuth flows; middleware provides JWT checks, validation, uploads, permissions, and response caching. The server also connects MongoDB and Redis and serves uploaded files. Several resource modules are represented from the tree and SOURCE INDEX, but their implementation details were not sampled, so the graph limits their internal links accordingly.
Main entry points: routes Resource routes · index.js Express app · redis/index.js Redis client · models Heritage models
Components 23
HTTP server
- Express app
index.js - Resource routes
src/routes - Request middleware
src/middlewares/index.js
Identity and access
- Auth routes
src/routes/auth.js - Auth operations
src/controller/auth.js - JWT strategy
src/common/strategy/jwt.js - JWT signing
src/utils/index.js - User operations
src/controller/user.js - User model
src/models/user.js
Heritage resources
- Event operations
src/controller/event.js - Historic-site operations
src/controller/historical_site.js - Lost-artifact operations
src/controller/lost_artefact.js - Museum operations
src/controller/museum.js - Site operations
src/controller/site.js - Art operations
src/controller/art.js - File operations
src/controller/file.js - Heritage models
src/models
Persistence and cache
- Mongo connector
src/db/db.js - MongoDB
- Redis client
src/redis/index.js - Redis
Other components
- API client
- Google OAuth
Connections 33
- API client → Express app: sends requests
- Express app → Resource routes: mounts routes
index.js - Express app → Auth routes: mounts routes
index.js - Express app → Mongo connector: connects database
index.js - Express app → Redis client: connects cache
index.js - Express app → Request middleware: registers handlers
index.js - Resource routes → Event operations: dispatches to
src/routes/event.js - Resource routes → Historic-site operations: dispatches to
src/routes/historical_site.js - Resource routes → Lost-artifact operations: dispatches to
src/routes/lost_artefact.js - Resource routes → Museum operations: dispatches to
src/routes/museum.js - Resource routes → Site operations: dispatches to
src/routes/site.js - Resource routes → Art operations: dispatches to
src/routes/art.js - Resource routes → File operations: dispatches to
src/routes/file.js - Auth routes → Auth operations: dispatches to
src/routes/auth.js - Auth routes → Request middleware: validates signup
src/routes/auth.js - Auth operations → User model: reads and writes
src/controller/auth.js - Auth operations → JWT signing: signs tokens
src/controller/auth.js - Auth operations → Google OAuth: exchanges OAuth code
src/controller/auth.js - JWT strategy → User model: loads user
src/common/strategy/jwt.js - Request middleware → User model: loads user
src/middlewares/index.js - Request middleware → Redis client: caches responses
src/middlewares/index.js - Resource routes → User operations: dispatches to
src/routes/user.js - Event operations → Heritage models: uses event model
src/controller/event.js - Historic-site operations → Heritage models: uses site model
src/controller/historical_site.js - Lost-artifact operations → Heritage models: uses artifact model
src/controller/lost_artefact.js - Museum operations → Heritage models: uses museum model
src/controller/museum.js - Site operations → Heritage models: uses site model
src/controller/site.js - File operations → Heritage models: uses file model
src/controller/file.js - Mongo connector → MongoDB: opens connection
src/db/db.js - Event operations → Redis client: uses cache
src/controller/event.js - Museum operations → Redis client: uses cache
src/controller/museum.js - Site operations → Redis client: uses cache
src/controller/site.js - Redis client → Redis: connects to
src/redis/index.js