How yenchenglai/expense-tracker-v2 works
Project type and purpose
• This is a full-stack web application (“expense-tracker-v2”) for personal/family expense tracking.
• Frontend: a React (Vite) SPA.
• Backend: two FastAPI microservices (auth-service and expense-service).
• Database: MongoDB.
• Purpose: allow users to sign up/log in, record and view expenses, manage settings.
File structure
• Top-level:
• backend/
– auth-service/app: authentication endpoints, user models, database connectivity.
– expense-service/app: expense CRUD endpoints, models, database connectivity.
– generate_hash.py, requirements.txt, makefile: utilities and build scripts.
• frontend/: React app under src/components, Vite config, package.json.
• docs/: architecture.md, deployment notes, requirements.
• Patterns:
• Microservices (auth vs expense).
• Clear separation of frontend vs backend.
• Each service has its own tests, README, and pytest config.
• Likely communicates via HTTP REST + JWT.
README for additional insights
• Stack: FastAPI, React, MongoDB.
• README references architecture.md in docs → likely contains more details.
• No monolithic backend: two independent services.