How vanshkapoor07/taskbuddy works
Project type and purpose
• This is a full-stack task management application named “TaskBuddy.”
• The frontend is a single-page React application (built with Vite).
• The backend is a Node.js/Express REST API backed by a SQL database (schema.sql / seed.sql).
• Core features: user authentication (JWT), task CRUD operations, team management.
File structure
• Top-level separation:
– frontend/ (React/Vite SPA)
– server/ (Express API)
– database/ (schema.sql, seed.sql)
– docs/ (API Endpoints, design notes)
• Frontend uses component-based MVC with pages, context for auth state, assets, and routing.
• Backend follows MVC: models (taskModel.js, userModel.js, teamModel.js), controllers (authController.js, taskController.js, teamController.js), routes (authRoutes.js, taskRoutes.js, teamRoutes.js), middleware (auth, validation, rate limiting, error handling), utils (encrypt, generateToken), and config/db.js to connect to the SQL database.
• Build/deploy scripts: package.json in both frontend and server; .env files for configuration.
README (empty here) and docs/API Endpoints.md
• The docs folder defines the REST endpoints for auth, tasks, and teams.
Detailed capture of essential architecture
• Call out the three core domains: Authentication, Task Management, Team Management.
• SQL database as a single relational store with schema/seed annotations.
• An annotation for environment/config (e.g., .env) feeding into both frontend (public config) and backend (DB URL, JWT secret).
• Error handling and rate limiting as cross-cutting middleware.