The MPD/CAVA configs stay generic via the mpd_local.conf include seam, so a fresh clone deploys cleanly. The systemd units don't have an equivalent: cava.service/crust.service hardcode User=jey, ExecStart=/home/jey/crust, and -p /home/jey/.config/cava/config. Today SETUP.md just tells you to edit them by hand before copying.
Worth exploring a cleaner seam:
- an untracked
EnvironmentFile= for User/paths,
- systemd specifiers (
%h, etc.),
- or a tiny install script that substitutes values on deploy.
Tradeoff: any of these adds machinery vs. a one-time manual edit. Low priority — documenting the edit points works fine for now.
The MPD/CAVA configs stay generic via the
mpd_local.confinclude seam, so a fresh clone deploys cleanly. The systemd units don't have an equivalent:cava.service/crust.servicehardcodeUser=jey,ExecStart=/home/jey/crust, and-p /home/jey/.config/cava/config. Today SETUP.md just tells you to edit them by hand before copying.Worth exploring a cleaner seam:
EnvironmentFile=forUser/paths,%h, etc.),Tradeoff: any of these adds machinery vs. a one-time manual edit. Low priority — documenting the edit points works fine for now.