-
Notifications
You must be signed in to change notification settings - Fork 1
Developer Update
Developer documentation. Full detail: docs/DEVELOPER_UPDATE.md — this page is a summary.
Three distinct concepts — don't conflate them:
A. Component updates (Klipper, Moonraker) — LIVE_HARDWARE_VERIFIED. Via Moonraker's own
Update Manager, backstopped by nebulaos-update-supervisor.sh (S59nebulaos-update-supervisor),
which health-checks after an update and can roll a component back. Two real bugs were found and
fixed during live testing of this path. A Moonraker-venv-versioning gap remains open.
B. Whole-image developer update — HISTORICALLY_HARDWARE_VERIFIED as a manual operator
sequence (build → transfer → flash-spare-slot.sh → marker flip → reboot; same steps as
Developer Install From Stock). There is currently no fully
automated release discovery, download, or whole-image updater.
C. Future OTA architecture — design-only, not implemented. See
docs/NEBULAOS_OTA_FLOW.md.
If an older document describes automated OTA as already working, treat §B as the authoritative
current state instead.
See also: A/B Slot Model, Developer Recovery.
Building
Install / update / recover
Reference