How qwe8851/yumseoul works
Project type and purpose
• This is a full-stack delivery application called “YumSeoul.”
• Frontend: React + Redux Toolkit + styled-components single-page app.
• Backend: Node.js/Express REST API with MongoDB (via Mongoose).
• Purpose: Users browse stores, view details, upload images, manage carts, and place orders. It includes authentication (JWT + bcrypt), password reset (crypto + nodemailer), and file uploads (Multer-S3 to AWS S3).
File structure
• Top level (backend):
• config/ – environment and DB configuration (development.js, production.js, mongo-db.js, key.js)
• models/ – Mongoose models (main, store, todo, upload, user)
• routes/ – Express routes for each resource (mains, stores, todos, uploads, users)
• public/ – static folder where the React build is served (index.html, manifest.json, robots.txt)
• server.js – application entry point, sets up Express, middleware, routes, and static serving.
• Frontend (yum-seoul-project):
• public/ – SPA host page (index.html)
• src/ – React app:
– components/ – reusable UI pieces (common, layout)
– pages/ – route components (Auth, Home, Main, Error)
– store/ – Redux slices (authSlice, storesSlice) and store setup
– utils/ – helpers (firebaseAuth)
– hooks/ – custom hooks (use-input)
– assets/, styles/ – CSS, fonts, styled-components
– App.js, index.js, routing, tests, build scripts
README for additional insights
• Technology stack and libraries (React, Redux Toolkit, styled-components, Node.js, MongoDB, Mongoose, bcrypt, JWT, Multer-S3, AWS S3, Nodemailer).
• Build instructions show that the React build is output into a folder served by the Node server.
• Implementation details: password hashing, AWS S3 uploads, email via SMTP.
Elements
• Clear labels (e.g., “React SPA,” “Express API,” “MongoDB,” “AWS S3,” “SMTP Server”)
• UI → API (data requests)
• API → DB (data reads/writes)
• API → S3 (upload)
• API → Email Service (send email)
• Blue for client components
• Green for server components
• Orange for database
• Gray for external services