musicmouse_version pointed both hosts at rearchitect-backend, a branch that only ever existed on a laptop - so the previous commit's rework could never actually have run. Point each host at a deploy/<host> branch on the remote instead. Those branches are the deployment record: what is installed on that box right now, moved with a force-push when you mean to deploy. musicmouse (Kinderzimmer) is the reason this matters. It is in daily use and still runs the pre-rearchitecture backend out of /opt/musicmouse_venv and espmusicmouse/host_driver/main.py. That commit has no python-backend/ pyproject.toml, no python-backend/musicmouse.service and no web/ at all, so this role cannot install it - and a run would have force-checked-out incompatible code over a working device first and failed afterwards. Set mediapi_install_kidsmusic: false there and leave it alone; deploy/musicmouse records the commit that is installed, for rollback. Add a stat + fail right after the checkout so the same mistake stops with an explanation instead of failing three tasks deeper. Also in the role: - Install the typing game's curriculum next to config.yml. A config with a tippen: section refuses to start without it - curriculum_file is validated as must-exist - so musicdolphin's new config needs it present. - Stop clobbering config.yml. The app writes to it at runtime: parent mode patches the volume keys and the remote-control page rewrites the remote: block. A plain copy: undid that on every run. Install-once by default, with -e pi_musicmouse_force_config=true to push a change deliberately. - Fill out config-musicdolphin.yml against the current schema: library root and cache, an absolute static_dir (../web/dist would resolve to /media/web/dist from /media/musicmouse and silently serve nothing), tippen, and the volume range for a screen-driven instance. ha: is left commented out until the Wohnzimmer-oben entity ids are picked - the ones in the dev config are Arbeitszimmer. No mqtt: (it would publish a device of dead entities on a simulate-only host) and no lirc:/remote: (this host runs irserver, a serial daemon, not the lircd this speaks TCP to). The curriculum is a verbatim copy of app content, so exclude it from ansible-lint rather than reformat it away from its source. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
26 lines
1.2 KiB
YAML
26 lines
1.2 KiB
YAML
---
|
|
squeezelite_name: MusicMouse
|
|
pi_shairport_name: MusicMouse
|
|
alsa_card_name: sndrpihifiberry
|
|
hifiberry_overlay: hifiberry-dacplus
|
|
sensor_room_name: Kinderzimmer
|
|
sensor_room_name_ascii: kinderzimmer
|
|
main_user: root
|
|
|
|
mediapi_has_hifiberry_amp: true
|
|
mediapi_install_bluetooth_monitor: true
|
|
# The Kinderzimmer device still runs the pre-rearchitecture backend (deploy/musicmouse
|
|
# == b2c060f): /opt/musicmouse_venv and espmusicmouse/host_driver/main.py, installed by
|
|
# an older version of this role. The current pi_musicmouse only knows the new
|
|
# python-backend/ + web/ layout, so it is deliberately off here - a run would
|
|
# force-check-out incompatible code over a device the kids use every day, and would
|
|
# fail anyway (that commit has no python-backend/pyproject.toml, no
|
|
# python-backend/musicmouse.service and no web/ at all).
|
|
#
|
|
# deploy/musicmouse stays recorded below as the rollback marker for what is actually
|
|
# installed. Turning this back on means migrating the device at the same time: move
|
|
# /media/musicmouse/<figure>/ into Figuren/ and switch to the new config schema -
|
|
# files/config-musicmouse.yml is already written for that.
|
|
mediapi_install_kidsmusic: false
|
|
musicmouse_version: deploy/musicmouse
|