How ash1998/expense-tracker works
Project type and purpose
• This is a self-hosted, full-stack web application for personal expense tracking.
• The Flask backend serves dynamic pages and REST endpoints; the frontend is a responsive UI built with Bootstrap, Chart.js and custom CSS/JS.
• Data is managed locally on disk (CSV/JSON per user) with pandas, avoiding any cloud dependencies.
File structure
Top-level components:
• app.py – main Flask application with route definitions and request handlers
• data/ – per-user data storage (CSV for transactions, JSON for settings)
• templates/ – Jinja2 HTML views (login, dashboard, analysis, settings, import/export, etc.)
• static/ – CSS (style.css), JS (main.js), images
• scripts/ – environment/config initialization for Windows, macOS, Unix; examples of .env and config.yaml
• requirements.txt – Python dependencies
• .env.example & config.yaml.example – environment and default settings
• docs/ – project documentation and screenshots
README for additional insights
• The README confirms a Flask-Login authentication layer, Flask-WTF forms, pandas for data manipulation, PyYAML for user config, Chart.js for interactive charts.
• It describes key features: authentication, CRUD for expenses, dashboard, analysis charts, settings, import/export, dark mode, responsive design.
• It notes MVC-style separation (routes, templates, static assets, and data logic).
Detail without over-segmentation
• Route group (auth, expenses CRUD, analysis, import/export) as sub-components if desired.
• Every directory with distinct responsibilities is represented.
• Don’t omit the data folder and config files – they are core to the local storage model.