Kofi E. Ampaabeng

Selected Work

20 systems I have architected, built and run: enterprise platforms, consumer apps, and the tools and infrastructure behind them. 20+ years across regulated banking, data platforms and applied ML.

20
systems
6
enterprise
7
ML · LLM
20+
years

15 · Compute and housekeeping

Shared container host

One shared host: every run capped, labelled, cleaned hourly.

One rootless-podman host takes every work session's containers and image builds over a remote engine connection; each run is labelled and capped, and an hourly housekeeper stops what is overdue and prunes what is unused.

  • Infrastructure

Surfaces

  • CLI
  • Self-hosted
  1. 01One host, one rule — every run and image build goes to one shared host over a remote engine connection; the workstation runs no engine.
  2. 02Runs expire by label — two hours by default, twelve at most; a keep label exempts a shared image.
  3. 03Hourly housekeeping — a systemd timer stops overdue containers, prunes unused images and cache, and clears everything unused above 80% disk.
  4. 04Rehearse first — each installer has a read-only rehearsal, and the housekeeper a dry run.
  5. 05Capped CI runners — runners live on build hosts only, never on the production host, with their caps written down.
  • 6 cleanup steps
  • 2 h default run lifetime
  • 80% disk trigger
SurfacesCLISelf-hosted
REQUESTCONNECTRUNCLEANRECORDbuild · runstop · pruneWork sessionsCI jobsEngine connectionremote podmanCapped runnerContainer hostrootlessLong-lived unitsQuadletHourly timersystemdHousekeeperHousekeeping log
Architecture, drawn from the codeServiceStoreModel usedModel trained hereFeedback
  • Podman (rootless)
  • Quadlet
  • systemd timers
  • GitLab Runner
  • Bash
  • Python