Viktor Petersson a9be1d3779 chore: drop pyzmq + libzmq, finalize ZMQ→Redis migration ...

With both legs of the viewer signalling path on Redis (PR1: command
bus, PR2: reply bus), the pyzmq runtime dependency and the libzmq*
build deps are no longer used.

- pyproject.toml: remove pyzmq==23.2.1 from server, viewer,
  wifi-connect, and mypy dep groups (4 places).
- uv.lock: regenerated; pyzmq + transitive py drop out.
- tools/image_builder/{__main__,utils}.py: remove libzmq3-dev /
  libzmq5-dev / libzmq5 from the base apt list and from the viewer
  context's apt list. docker/uv-builder.j2 likewise drops libzmq3-dev
  from both the prebuilt-uv branch and the pip-fallback branch (32-bit
  ARM). The rendered docker/Dockerfile.* artifacts are gitignored, so
  no committed Dockerfile churn here — they regenerate cleanly via
  `python -m tools.image_builder --dockerfiles-only`.
- send_zmq_message.py → send_viewer_message.py. The script already
  publishes via Redis (fixed in the PR1 follow-up); rename + update
  callers (bin/start_wifi_connect.sh, docker/Dockerfile.wifi-connect.j2)
  now that the ZMQ name is misleading.
- bin/start_server.sh: drop the stale "single-worker because
  ZmqPublisher binds 10001" comment. The publisher is now a Redis
  client — no port bind, multi-worker is safe whenever the operator
  wants to opt in (not changed in this PR).
- CLAUDE.md: update the architecture description (ZMQ ports 10001 /
  5558 are gone, Redis carries the viewer signalling traffic now).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-27 17:06:04 +00:00

..

image_builder

chore: drop pyzmq + libzmq, finalize ZMQ→Redis migration

2026-04-27 17:06:04 +00:00

__init__.py

…

migrate_assets_to_screenly.py

ci: enforce strict mypy across the codebase (#2752)

2026-04-27 14:53:37 +01:00