AutoStopper

Added

• AutoStopper talks to the Docker Engine API directly over the Unix socket or plain TCP, so the proxy no longer needs the Docker CLI. The new docker.backend (auto, api, cli) and docker.endpoint (auto, unix://…, tcp://…) settings are validated on load and reload. backend: auto uses the API, finding the daemon through DOCKER_HOST, then an autostopper-docker socket-proxy sidecar, then /var/run/docker.sock. It falls back to the CLI for ssh:// or TLS DOCKER_HOST, a selected Docker context, or Windows. The selected backend and endpoint are logged and shown at the end of /autostopper status. Existing deployments that mount the Docker socket keep working unchanged (#143).

Changed

• The examples give Velocity Docker access through an autostopper-docker socket proxy (wollomatic/socket-proxy, pinned by digest) on an internal network. The proxy allows only container inspect, start, and stop, and only from the velocity service. Velocity runs the stock itzg/mc-proxy image with no custom entrypoint, no socket mount, and no host-specific values. The README, security, troubleshooting, and configuration docs describe this setup, and a new 2.2.0 to 2.3.0 migration guide covers moving an existing deployment. The custom docker-entrypoint.sh pattern and the Docker CLI backend (docker.backend: cli) are deprecated and planned for removal in 3.0.0. Mounting the socket directly remains supported (#144).
• The examples and README install AutoStopper from Modrinth at startup through the proxy image's MODRINTH_PROJECTS, pinned to one release, with MINECRAFT_VERSION set as the image requires. There is no JAR to download; upgrading means changing the pin. The proxy contacts Modrinth on every start. Installing the JAR manually remains documented as the alternative; use one method only (#142).

Removed

• docker-entrypoint.sh from the examples. Existing deployments that use it keep working (#144).