How kanmikan/c-chan works
Main system components
• Client (web browser)
• Web server (Node.js/Express)
• HTTP Server & Static asset serving
• View Renderer (EJS templates under client/views)
• API Layer (server/api/*.js + server/api/*.js modules)
• Business Logic & Middleware (server/routes.js, server/utils.js, server/sesion/, server/extra/)
• Data Access Layer (server/db/*: cache.js, dbmanager.js, models/)
• Database (MongoDB Atlas or local)
• External Services
• YouTube API
• Cloudinary or ImgBB
• Background Bots & Cron threads (server/extra/*.js, controlled via CRON_THREADS)
Relationships & data flows
• Browser → HTTPS → Express Router
• Router applies middleware (session management, rate limiter, sanitizer)
• Depending on the request:
• Static GET (CSS/JS/images) → Express static middleware (client/static/)
• View requests → EJS renderer uses views + fragments → HTML → Browser
• API calls → server/api modules → business logic → DB or external service → JSON response
• DB access flows: Express → dbmanager.js → specific model schemes → MongoDB
• External calls: API modules call YouTube, Cloudinary or ImgBB SDKs, return data to controllers
• Bots/Cron threads run independently, access the same DB & push content/alerts
Architectural patterns & design principles
• MVC-like separation:
• Models: server/db/models/*
• Views: client/views/*.ejs
• Controllers: server/api/*.js & server/routes.js
• Layered pattern:
• Presentation → Business → Data Access → Database
• Middleware pattern for cross-cutting concerns (sessions, sanitization, limiting)
• Plugin-style extensions via server/extra bots