---
pi_musicmouse_repo: "ssh://git@git.bauer.tech:2222/martin/musicmouse.git"
# No default on purpose: which branch to run is a per-host decision, set in host_vars.
# The deploy/<host> branches on the remote are the intended values - move one with
# `git push -f origin <branch>:deploy/musicdolphin` and re-run this role.
# musicmouse_version: "deploy/musicdolphin"

pi_musicmouse_python_version: "3.13"
pi_musicmouse_uv_version: "0.12.10"

# Where to check out the repo on the *control machine* to build the frontend (npm isn't
# installed on the Pi - see README). Keyed by version so different hosts on different
# versions don't clobber each other's build.
pi_musicmouse_build_cache: "/tmp/musicmouse-build-cache"

# Which files/config-*.yml to install as this host's /media/musicmouse/config.yml.
pi_musicmouse_config_file: "config-{{ inventory_hostname }}.yml"

# The app owns config.yml at runtime: parent mode writes the volume keys back to it, and
# the remote-control page rewrites its `remote:` block. So the config is installed once
# and then left alone, or every ansible run would silently undo those edits. Push a
# changed config deliberately:
#
#   just run mediapis.yml musicdolphin -e pi_musicmouse_force_config=true
pi_musicmouse_force_config: false

# The typing game's lesson plan, installed next to config.yml. A config with a `tippen:`
# section will not start without it - curriculum_file is validated as must-exist. Set to
# "" for a host whose config has no tippen section.
pi_musicmouse_curriculum_file: "tippen-curriculum.yml"