Project 2 — Expense tracker in Go (Golang)
Built by feature: one folder per concept. Accounts, passwords and login, taught inside the project that needs them.
- 01Project 2 — Expense tracker: what we are buildingA money app with accounts, which is why this is where login belongs.
- 02Step 1 — Setup, config, and the schemaFail at startup rather than at 3am, and let the database enforce what it can.
- 03Step 2 — Register: storing a password safelyWhat hashing is, why you can never read a password back, and how bcrypt works.
- 04Step 3 — Login and what a token isCheck a password without unhashing it, and hand back proof for the next request.
- 05Step 4 — Checking the token on every requestOne middleware, at the edge, so no handler ever has to remember.
- 06Step 5 — Expenses, locked to their ownerCRUD again, but now every query has to know whose data it is.
- 07Step 6 — Filtering, paging, and a monthly reportLet the database do the counting, and never return an unbounded list.
- 08Step 7 — Refresh tokens and logoutMake sessions endable, without a database lookup on every request.
- 09Step 8 — Test that the walls actually holdOne test here matters more than the rest: the one that proves users are kept apart.