What it does
Container packaging for the things worth running on your own server: the always-on services — ATEM Overseer, RFutils, caspar-AV, srt-router, flock — and the browser tools, which are static pages you would self-host so they still work in a venue with no internet.
Deliberately not the plugin browser demos or the public websites: a demo shows what an effect looks like and a marketing site is already deployed, so neither is something anyone would install. Nothing is written by hand — two data files describe the fleet and two scripts turn them into the 74 files spread across the app repos, committed so every generated file is reviewable in history rather than produced at build time.
- Dockerfiles and compose files generated from fleet.json
- Unraid Community Applications templates generated from unraid.json
- Deterministic generators, with their output committed and reviewable
- Images built by GitHub Actions on every push
- Scoped to the apps someone would actually self-host
Where it stands
In development. A green CI run proves an image builds — it does not prove the app inside it serves correctly, and no container has been installed on a real Unraid server from these templates. The machine these files were written on has no container runtime and no nginx, so nothing here has ever been built, started or requested locally.