v1.3.0 — Multiple Docker hosts + simpler connect model

Builds on the v1.2.0 Docker label provider with multi-host support and a much simpler connect model.

Added

• Multiple Docker hosts. Watch several daemons at once. Configure a JSON list of endpoints (QG_DOCKER_ENDPOINTS, or the Docker hosts box on the Docker page), each with a name, a connect (a local socket path or tcp://host:port), and the address where that host's published ports are reachable. A container on a remote host is reached at that host's IP. The Docker page shows each host's connection state and labels every container with its host.
• The Docker client now speaks tcp:// endpoints in addition to unix sockets, so you can point it at a read-only socket proxy.

Changed

• Simpler connect model. quicgate now always reaches a container at the Docker host's address on its published port (a network_mode: host container at that port directly). The auto / network / published connect-mode and the shared-network container-IP path are gone. quicgate.port still names the container's internal port, so publish the port you want routed.

Reach remote daemons through a read-only socket proxy (e.g. tecnativa/docker-socket-proxy with only CONTAINERS=1 and EVENTS=1) so quicgate never gets write access. See the Docker labels docs.