House-move inventory: Status, going? and a history - Part 11
~8 min read
A box has a status: packing, sealed, in transit, arrived, unpacked. That was in the very first design. What I hadn't predicted was how much a move is also a long series of decisions about things that aren't packed at all. This post is about the two extra fields that grew onto boxes, the history that records them, and a rule about dependent fields that I'd defend in a code review.
Two independent axes
Status is the physical lifecycle: packing → sealed → in_transit → arrived → unpa
Personal finance aggregator: Cash, and an audit trail - Part 18
~7 min read
Everything the app tracks so far lives somewhere with an API, or at least a login: banks through TrueLayer, Hargreaves Lansdown through its website, and loans typed in by hand as manual accounts. The one pot of money it couldn't see was the physical kind - the notes and coins in a wallet or a drawer. Four commits close that gap and then answer a question it raised: when a balance changes, why? This post covers the cash account type (add full cash tracking account type, reduce cash d
House-move inventory: Built, then deleted: authentication - Part 10
~8 min read
For a two-person app, a login system sounds like overkill. I built one anyway, over about three weeks, and then removed all of it. This post is the history, and what the app trusts today.
(If you've read the finance-system series, its post 9 "Handing authentication to identity-system" covers the same destination reached from a different starting point.)
Built it
On 6 September, Phase 3.9 added per-user accounts and server-side sessions with Argon2 hashing, a POST /api/auth/login
Personal finance aggregator: Making the nightly sync boring - Part 17
~9 min read
The goal of a nightly job is to be boring. Nothing about it should be worth reading about. By early October the sync was no longer a script I ran by hand (post 3) but a multi-user, multi-provider pipeline, and getting it to quiet took a run of unglamorous commits. This post gathers them, from systemd units to log retention to two small test fixes. If the earlier posts were about adding capabilities, this one is about the failure modes that appear once the capabilities are live.
Mo
House-move inventory: Slow PDFs as background jobs - Part 9
~8 min read
By the end of September the room PDF could do a lot: a summary page, every box's contents, each box's photo and each item's photo, then every invoice attachment merged on the end. It was also taking long enough that production started returning 504s - the reverse proxy gave up before the PDF finished.
This post is about the fix, and about a decision I'm glad I made: not putting it in the database.
First, the cheap fix (and why it wasn't enough)
The first reaction is to raise the
Personal finance aggregator: Savings projections - Part 16
~8 min read
Everything so far has looked backwards: what I spent, what I owe, what the balance was. The savings and projection commit and its follow-up (build on savings add anni date) look forward. The Savings page takes any savings account - synced or manual - and projects its balance twelve months out, given an interest rate and a monthly contribution. It's a small amount of maths, and nearly all of the interest is in making the assumptions explicit, so this post is mostly about those.
The
House-move inventory: Sheets, labels and French - Part 8
~9 min read
The inventory only does its job if it leaves the screen. A sheet goes inside each box. A label goes on the outside. Customs gets a document, and since the move is to France, the document is in French. This post covers the rendering layer and the project's only outbound network call.
Pure formatting over domain objects
render/ holds three modules:
* sheets.py - the plain-text contents sheet.
* pdf.py - PDFs with reportlab: a box sheet, a room sheet, and /labels.pdf, A4 pages of
Jenkins shared library: Linting and unit testing the library - Part 4
~8 min read
A shared library is the one place where a mistake reaches every pipeline at once. A typo in syncBlog doesn't break one build, it breaks every project that calls it the next time they load the library. That makes it the code in my setup that most deserves a safety net, and so far it had none. This post adds two: CodeNarc for linting, and unit tests, both run by the library's own Jenkinsfile.
A Gradle build that only does tooling
The library itself needs no build. Jenkins loads it
Marketplace Listing Helper: Linking listings that already exist - Part 7
~5 min read
The extension was built to create listings, but plenty of my stock was already on Marketplace before the extension existed. Those items sat in the list as drafts, with nothing to say they were live: no "listed" date, no renew reminder, and a real risk of posting them twice. I wanted to say "this listing is that item".
What "link" means
Linking records the address of the Facebook listing on the item. That's all. It's a new column, fb_url, which exports with the CSV like any other.
~9 min read
Categorised spending answers "where did it go?". A budget answers the more useful question, "am I on track?". This post covers the Budgets page, built across five commits between 1 and 5 October, and extended in mid-October with a 50/30/20 view and a richer category page. Nearly all of it reuses machinery from post 12, which is the point - the interesting new decision is about time, not categories.
A month, but whose month?
A budget needs a period, and the obvious period is the c
House-move inventory: Invoices, photos and HEIC - Part 7
~8 min read
A list of items tells customs what. An invoice tells them how much, and that it's real. And a photo of the item, or of the box before it was packed, answers every "which sofa was that?" argument. Both are files, and files don't belong in a SQLite database. This post covers where they went, and one surprisingly fiddly format.
Bytes outside the DB
Attachment bytes live on disk, next to the database, in <db dir>/attachments/ (override with $INVENTORY_ATTACHMENTS_DIR). The database s
Jenkins shared library: Shared defaults and a package name - Part 3
~5 min read
The first version of syncBlog had its release tag written straight into the step: v0.2.0 as a default, the Ghost repository URL inside the shell snippet, and the two credential IDs as string literals. That works for one step. This post is about moving those values somewhere central, and about the package name I put them under.
Where to keep a shared value
I weighed three places:
* The default in the step. Simplest. Bump it, tag the library, and every project that doesn't pass v