How the-seven-js/fptu-clothing-be works
Project type and purpose
• From the file tree we see a Dockerfile, a GitHub Actions CI/CD workflow, package.json, and a src/ directory structured into controllers, routes, middleware and config. The presence of JSON “advice” files and “attribute_data” suggests this is a standalone Node.js/Express RESTful API service that delivers “male” and “female” advice data, handles articles, comments, photo uploads, and authentication flows (login, logout, change-password).
File structure
• Top-level:
• Dockerfile and .github/workflows/cicd.yml → containerization & CI/CD pipeline
• package.json / package-lock.json → Node.js + npm modules
• src/ → application code
• uploads/ → persistent storage for user-uploaded photos
• src/ subfolders:
• config/db.js → database connection settings
• controllers/*.js → business logic for articles, comments, demos, photos
• routes/*.js → Express routing definitions, mapping HTTP endpoints to controllers
• middleware/authmiddleware.js → authentication/authorization logic
• static JSON files (male_advice.json, female_advice.json, attribute_data_*.json) → data fixtures
README
• The README (“aNH qUÝ âm vô cực điểm”) contains no architectural guidance. All insights must come from the file layout and naming conventions.