Three packages in this Emacs config are installed the same way: skip the archive-based package manager, fetch straight from GitHub with package-vc-install, and guard the call so it only ever runs once.
In CaRMen, my CRM, every deal has an owner and every activity has an assignee: a user. For a while the deal list showed "-" in the Owner column for every deal, which looked like a display bug. It was worse than that. Opening a deal and saving it, without touching the owner field, removed the owner from the deal. The same happened to an activity's assignee.
Parts 2 to 4 were about building the search engine: getting pages, deciding which ones count, computing authority.
On the database server of my search engine project, /etc/ssh/sshd_config said PasswordAuthentication no. The server accepted password logins anyway, and a bot on the internet was guessing the root password around the clock. Every attempt failed, but only because the password held, not because the setting did.
CaRMen, the small CRM I run for myself, had unit and controller tests from early on, but nothing that drove an actual browser against the actual frontend until October. Setting up Playwright properly — @playwright/test instead of plain playwright, a Chromium-only project, role-based locators, a shared login helper — took one evening.
Part 3 ended on an assumption: that the authority score behind every ranking was right. Authority comes from PageRank, computed over the whole link graph, and it's the part of this search engine that has never fitted comfortably anywhere.
The script that drafts and schedules articles for this site starts a self-hosted LanguageTool server for each run, so every draft gets a grammar check before it's published. On 15 October, on the LFS laptop it now runs on, I found that LanguageTool hadn't started at all, and nothing in the script's output said so.
I wrote a piece in September about this site's average Google Search Console position falling from the 14-20 range to 7.8-9.4, right as a dozen new articles went live.
I run a small CRM for myself called CaRMen — a Symfony 7 API Platform backend with a React frontend. In August I had to bump api-platform/core from ^3.3 to ^4.0, not because I wanted the new major version, but because composer's own security-advisory audit flagged every 3.3.x and 3.4.x release in a row. There was no patched 3.x left to stay on.
My PHP projects don't run PHP on the host. This site runs in DDEV, CaRMen runs in a docker compose stack, and whatever PHP the host has is irrelevant to both.