Skip to content

Build logs from a small estate#

I run a self-hosted homelab I call WOPR: one Proxmox host, a ZFS pool, a few dozen containers, and the software I have written to run on it. Some of that software has grown from a weekend build into something I depend on. When that happens I write the build log: what I set out to do, what got built and in what order, what broke, how I found out, and what I would tell someone starting the same thing.

The logs are written from the record, not from memory. Every date, count and feature cites the commit that introduced it, in backticks like ff18acc, or the document it comes from. Where the record is silent, the log says so. Much of the code was written by Claude under my direction; the logs say where.

  • doe

    active

    2026-07-12 →2026-09-27 ·243 commits ·Flask · PostgreSQL · gunicorn

    An exam and study platform. MCQ and flashcard "quick test" cards, AI grading, spaced repetition and a sourced question corpus. Used for my own Open University study, and by one other learner.

    • study
    • exams
    • llm
    • postgres
    Read the build log

  • treasury

    active

    2026-07-03 →2026-09-25 ·115 commits ·Python ETL · PostgreSQL · Flask

    A personal finance pipeline. Bank and receipt ETL into PostgreSQL, and a web app for budgets, pots and projections. Forked off the same container as doe.

    • finance
    • etl
    • postgres
    Read the build log