v0.4.0

Highlights

Disabling a component now actually removes it: its services stop on the next
upgrade, where they used to keep running, just no longer updated.

• Components: a disable is carried out by the next upgrade (#16).
• Settings page: also reachable through odio's main web UI (#12).

⚠️ Components disabled before this release are still running

odioctl used to only stop updating a component you disabled: its services kept
running. This release does not go back over them. To stop one, enable it, apply
the upgrade, then disable it and apply again.

🎵 Components

• Disabling a component marks it "on its way out": the upgrade card lists it,
  and Apply stops its services before the rest of the upgrade runs. Until
  then, one click on the component keeps it.
• Disabling a role takes its features with it. Enabling it again later brings
  them back.
• If the removal fails, nothing else runs and the component stays pending:
  the next Apply tries again.
• The list of components, their groups, labels and versions all come from the
  odios release: a new role shows up without a new odioctl.
• The Audio group opens with the audio server in use. It is PulseAudio for
  now; once an odios release offers PipeWire, it becomes a choice there.

🖥️ Settings page

• odio's main web UI can serve the page under its own address, so it no longer
  needs port 8021. Port 8021 still works.

🔧 Under the hood

• odios now records each install through odioctl (odioctl state record), and
  reads it back with odioctl state show.
• The login banner is odioctl motd, no longer a script that started Python at
  every login.
• The DAC block goes first in config.txt (already in 0.3.2).

Full Changelog: v0.3.2...v0.4.0