Developer Update

Updating a NebulaOS device

Full detail lives in docs/DEVELOPER_UPDATE.md — this page is the short version.

There are two kinds of updates, and it's easy to mix them up:

Klipper and Moonraker update through Moonraker's own Update Manager — same as any normal Klipper setup — backed by a small supervisor script that health-checks after an update and can roll a component back if it breaks. We found and fixed two real bugs testing this live. One open item: Moonraker's Python virtualenv isn't independently versioned or rolled back yet.

The whole OS image updates manually — same steps as Developer Install From Stock: build, transfer, flash-spare-slot.sh, flip the marker, reboot. There's no "check for updates and install" button yet — every step is something you run by hand.

There's a design for a more automated update flow down the road (see docs/NEBULAOS_OTA_FLOW.md), but that's a plan, not something that exists today. If an older doc describes automatic OTA as already working, this page is the current, accurate state instead.

See also: A/B Slot Model, Developer Recovery.