Expense-Tracker

Series links: Part 1/5 – Introduction Part 2/5 – Database Planning Part 3/5 – AWS Setup Part 4/5 – Backend APIs Part 5/5 – Frontend (you are here) What A small, fast web app that helps you add transactions with bills and later search/export them. Why Quick to use on phone or laptop. No heavy frameworks needed; it’s plain HTML/CSS/JS so you can host it anywhere. How Get the code Frontend source: https://github.com/sagarnayak/expense-tracking-public Pages you’ll see ...

Series links: Part 1/5 – Introduction Part 2/5 – Database Planning Part 3/5 – AWS Setup Part 4/5 – Backend APIs (you are here) Part 5/5 – Frontend What A tiny set of APIs to save entries with files, search them, get suggestions, and export CSV. Why Clear, stable contracts make the frontend simple. You can implement these endpoints in any backend framework. How Use your own domain names. The example hostnames below are placeholders. ...

Series links: Part 1/5 – Introduction Part 2/5 – Database Planning Part 3/5 – AWS Setup (you are here) Part 4/5 – Backend APIs Part 5/5 – Frontend What A light AWS setup to hold two things: your files (bills) and your data (transactions). Why S3 is reliable and affordable for documents/photos. RDS PostgreSQL gives you a managed database without running servers. How S3 bucket for web hosting (public read) Create a bucket for the static site (e.g., my-expenses-web). Make it public-read so the HTML/CSS/JS can be fetched by browsers. Optionally use CloudFront in front; with OAC you can keep the bucket private and still serve publicly via the CDN. Alternative hosts: Netlify, Vercel, or any simple web server. S3 bucket for documents (private) ...

Series links: Part 1/5 – Introduction Part 2/5 – Database Planning (you are here) Part 3/5 – AWS Setup Part 4/5 – Backend APIs Part 5/5 – Frontend What A minimal PostgreSQL structure with just two tables: one for the transaction entry and one for the attached documents (bills/receipts). Why Keep it simple so you can start quickly. Easy to query, filter by date/text, and export. How Tables at a glance accounting_entry: one row per transaction (expense or income). ...

Series links: Part 1/5 – Introduction (you are here) Part 2/5 – Database Planning Part 3/5 – AWS Setup Part 4/5 – Backend APIs Part 5/5 – Frontend What A small, practical expense tracker you can run yourself. You pick a date, enter amount (Credit/Debit), add a category and description, attach bill photos or files, and submit. Later you can search by text/date and export a CSV for your accountant. Why Keep all receipts and notes in one place with the transactions. Search quickly when you need proof or totals. Download a clean CSV and share it with your CA. How The system has three pieces: Database (PostgreSQL) to store entries and attached documents. Backend (Java) with simple APIs to save, list/filter, autocomplete, and export. Frontend (static HTML + JS) with three screens: Login, Add Entry, Listing/Export. Typical flow (with screenshots): Step 1 — Login ...