How deepshah232004/fitnest works
Project type and purpose
• This is a full-stack, fitness-focused web application (FitNest) that combines:
• A single-page front-end (React + Vite) for user interaction,
• One or more back-end services (Node.js & Python) for data persistence, chat functionality, and pose-estimation,
• A MongoDB database for storing user profiles, workouts, etc.
File structure
Top-level folders and their roles:
• fitNest/ – the React-Vite front-end (JSX, CSS, assets, routing, stateful UI)
• mongoDB/ – Node-based API server (Express, Mongoose models, REST endpoints)
• model/ – Python service (Flask or FastAPI) exposing pose_estimation endpoints, using a YOLOv8 model
• chatbot/ – dual Node.js and Python chatbot service interacting with products.csv, possibly calling the model or DB
• root package.json & package-lock.json – monorepo scripts or shared dependencies
• venv/ & fitNest/node_modules/ & mongoDB/node_modules/ – language-specific environments
Patterns & hints:
• Microservices style: separate folders → separate containers/services
• SPA front-end talking to back-ends over HTTP/REST
• Data persistence via MongoDB
README for additional insights
• Minimal README (“# FitNest”) but folder names and files reveal tech stack and service boundaries.
Detail without over-splitting
• Service as its own component
• Don’t break UI further than “FitNest SPA” unless you want separate “Authentication” and “Dashboard” sub-components