kami 5d1850c203 fix: mavwaked is a client binary, not a docker daemon
- Revert Dockerfile: no mavwaked build, no alsa-utils runtime dep
- Revert .dockerignore: no /mavwaked entry
- PROGRESS.md: deploy note says systemd user unit on a client box
  (desk PC, pi), connects to mavend over wg or local net — never on
  the homesrv or in docker
2026-07-06 14:12:33 +04:00
2026-07-03 00:32:48 +02:00
2026-07-03 00:32:48 +02:00
2026-07-03 00:32:48 +02:00
S
Description
No description provided
70 MiB
Languages
Go 97.1%
HTML 0.9%
Shell 0.6%
CSS 0.5%
Makefile 0.3%
Other 0.6%