How gautam23145032/personalfinancetracker works
Project Type & Purpose
• This is a full-stack personal finance tracker web app.
• Frontend: static HTML/CSS/JS (index.html, style.css, script.js).
• Backend: Node.js + Express REST API (server.js, routes/transactions.js), Mongoose models for MongoDB.
• Purpose: allow users to add, view, delete transactions, filter by date, and calculate summary stats.
File Structure Analysis
• Top-level:
• backend/ – server code, API routes, Mongoose models, environment config
• frontend/ – client‐side UI and logic
• Patterns:
• MVC-lite on backend (models/, routes/, server entry point)
• Client–server separation (vanilla JS calling HTTP endpoints)
• Deployment/config:
• .env for MONGO_URI & PORT
• package.json scripts for startup
• No containerization files (can be added later)
a. Frontend
• Browser or static‐hosted UI
• script.js makes HTTP requests to /api/transactions
b. Backend
• Express server (server.js)
• Route layer (transactions.js)
• Model layer (Transaction.js via Mongoose)
• Middleware: CORS, dotenv
c. Database
• MongoDB Atlas (external service)
• Connected via MONGO_URI
d. External Services (optional)
• Static file host (GitHub Pages or similar)
• Future: Auth service (JWT), Chart.js, CSV/PDF export library
Relationships & Data Flow
1. User opens index.html in browser
2. script.js → HTTP GET/POST/DELETE → Express API (http://localhost:3000/api/transactions)
3. Express routes invoke Mongoose models → MongoDB queries
4. MongoDB returns data → Express sends JSON response → script.js updates UI
5. UI renders transaction list & summary
Architectural Patterns & Design Principles
• Separation of concerns: UI vs API vs data persistence
• RESTful API design for CRUD operations
• Environment-driven configuration (dotenv)
• Model abstraction with Mongoose schemas
• CORS to allow cross-origin frontend calls