How hieuchichau/danagreen works
Project type and purpose
• This is a full-stack web application comprised of:
• A user‐facing frontend (“frontend” folder, React + Vite)
• An admin console frontend (“admin” folder, React + Vite)
• A Node.js/Express backend REST API (“backend” folder)
• Purpose: Manage events, vouchers, users, histories, support requests.
File structure
• Top-level:
• admin/ → React admin dashboard
• frontend/ → React public site and user dashboard
• backend/ → Express server, controllers, models, routes, config
• Backend uses MVC: models/, controllers/, routes/
• Config: database connection (db.js), Cloudinary integration, .env files, SSL certs
• Storage: local “uploads/” folder + Cloudinary for images
README
• Rely on folder naming, config files, and code layout to infer components
Main components and interactions
1. Admin Frontend (React/Vite)
2. User Frontend (React/Vite)
3. Backend REST API (Node.js + Express)
4. Database (MongoDB or other)
5. Local File Storage (“uploads/” directory)
6. External Image Storage (Cloudinary)
7. Authentication (JWT middleware)
• Frontends → Backend API: HTTP/HTTPS requests for auth, CRUD operations on users, events, vouchers, histories, support, images
• Backend → Database: read/write via Mongoose models (userModel, eventModel, etc.)
• Backend → Local Storage: write uploaded files into /uploads (via ImageUploadController)
• Backend → Cloudinary: upload and fetch image URLs (via cloudinary.js config)
• Backend → Frontends: JSON responses (data, status codes)
• Frontends → 3rd‐party APIs (if any – e.g. QR code scanning library)
c. Architectural patterns & design principles:
• Three-tier architecture (UI, API, Persistence)
• RESTful controllers & routes (separation of concerns)
• JWT‐based stateless auth (auth middleware protects routes)
• Component-based UI (React) with centralized API modules under src/api
• Environment configuration via .env in each app
d. Key technologies/frameworks (annotate each component):
• React + Vite (admin & user UIs)
• Axios or fetch (src/api/*.js → HTTP client)
• Node.js + Express (backend/server.js)
• Mongoose or native MongoDB (models/*.js)
• Cloudinary SDK (config/cloudinary.js)
• JSON sample files (backend/config/*.json) for initial seed data
• SSL certificates (key.pem, cert.pem) for HTTPS