Versions registered here are served at /firmware/<version-id>/
as index.json + per-version manifest.json
(plus legacy text files during the device-update transition).
Upload a release bundle or bootsystem squashfs
Choose the image build's defend-o-tron-<arch>.bundle
(only its bootsystem-current.squashfs is sent) or a
bootsystem squashfs, and it streams straight to the CDN.
The console probes the nested rootfs for the kernel release and
codename, computes the sha256 + size, and writes and signs
manifest.json + index.json on publish.
Once published, Download bundle on its row gives the
signed bundle for the installer and netboot builds.
Confirm & publish
Register a version
For artifacts placed under $CDN_ROOT/firmware/<version-id>/
out-of-band (rsync/cp). The server probes the squashfs for kernel +
codename (override below if probing can't run) and writes the manifest.
Scan CDN tree
Reconcile version directories under $CDN_ROOT/firmware/:
probe each squashfs for kernel + codename, (re)generate
manifest.json per version, and rebuild
index.json (+ legacy available.txt).
latest.txt is left untouched — promote a version
explicitly via the row action below.
The steps that a unit runs after it gets this firmware. The console
checks each step with the same rules that the unit uses. If a check
fails, nothing is saved. The list goes into the signed
manifest.json of this version.