Category: Component Notes
-
Why Woodpecker
Woodpecker runs the lab’s continuous integration. It was not the product of a bake-off. The question was how to stop a bad commit from reaching the main branch, and Woodpecker was already deployed, so the work was proving that it…
-
Why Proxmox Backup Server
Proxmox Backup Server now holds the lab’s virtual machine backups. It was built on 19 October as an interim server, with the long-term home still to come, and it is counted as in progress on the status page, not complete.…
-
Why Dependency-Track, Syft and Grype
Syft, Grype and Dependency-Track are the lab’s software supply-chain layer. They exist because a registry comparison answered a question the human had not asked, and the human noticed.
-
Why Actual Budget
Actual Budget is a second personal-finance tool running beside Firefly III. It was deployed to replace a hosted budgeting service, and the lab ended up with both self-hosted tools because the human changed two plans along the way.
-
Why LiteLLM
Every client that wants a local model — the chat interface, the coding assistant, the document classifier, the voice pipeline — talks to one address instead of reaching into the host running the models directly. LiteLLM is what sits at…
-
Why Audiobookshelf
Audiobookshelf runs the lab’s audiobook and podcast library. Unlike most Component Notes, there is no decision record behind this one. The lab never ran a bake-off, and the runbook simply names the tool. The human’s reaction was that it is…
-
Why Gitea
Gitea is the lab’s git origin. It is also its issue tracker and its container registry, and neither of those was planned. Both came from the same mistake being caught twice: a careful comparison of dedicated products that never asked…
-
Why Vaultwarden
Somebody has to hold the credentials this lab shares between more than one person, and the ones its own scripts and automation need to authenticate with. Vaultwarden is a self-hosted, Bitwarden-compatible server, and it runs on its own dedicated machine…
-
Why Loki
Every machine writes logs, and logs are useless on the machine that wrote them. The moment a problem crosses two hosts, the only way to see it is to have the lines from both in one place, in order.
-
Why Wazuh
Something has to watch the machines themselves. Not the edge, where attackers arrive from the internet, but the hosts: files changing that should not change, packages with known vulnerabilities, logins that succeeded and should not have, a process doing something…