The same observability shape rolled out to all five FastAPI backends — homelab-sacenpapier, PopRoom, BotWhy, Apercu, and x: a `/metrics` endpoint via `prometheus-fastapi-instrumentator`, an `/api/health` check, and one app-specific business gauge per app that a pure infra-level check can't see. Each app gets its own NodePort metrics Service and a Prometheus scrape job on `tspi`, tagged with a `project` label.
A per-IP rate limit (20 requests/minute via `slowapi`) and a 500-character message length cap on BotWhy's `/openai/answer` endpoint — the one route that actually calls out to a paid AI provider on every request.
A `CookieConsent` component for the frontend, and a real rewrite of how trending conversations track likes and comments: per-user like tracking (instead of a bare counter), unlike, and comment add/delete endpoints.
The founding build of BotWhy: a conversation/messages API, the first chatbox pages, request validation, a mobile-responsive layout, and the first Docker-based deployment — landing as one continuous week of work right after Google auth (and its [FedCM migration](/updates/2024-08-06-botwhy-fedcm-migration)) gave the app somewhere to attach a conversation to.
The actual foundation of Apercu: a full rebuild in April 2024 from an earlier Create React App prototype onto Docker + React + FastAPI + MySQL, with a contact form that sends real email, an admin "agent" interface for managing the underlying data, password hashing, and a first (later superseded) forget-password flow.
The founding build of what would become x: a three-section layout, tweets (post/view), follow/following with a suggestions feed, per-tweet likes, profile editing, a seeded database for local dev, and the first Docker-based deployment — all landing as one continuous build over the project's first three weeks, alongside direct messages ([written up separately](/updates/2024-05-19-x-direct-messages)).