fix: require Docker Compose v2 in scripts and docs

compose 1.29.2 aborts with KeyError: 'ContainerConfig' against Docker 28,
which broke the deploy on the prod VM.

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

README.md

@@ -6,6 +6,10 @@ TLS certificates are issued and renewed automatically by Let's Encrypt — no ce
 
 ## Quick Start
 
+> Requires Docker Compose **v2** (`docker compose`). The legacy `docker-compose` 1.29.x fails on Docker 28 with `KeyError: 'ContainerConfig'`.
+>
+> `apt-get install -y docker-compose-v2`
+
 ### Prerequisites
 - Ubuntu 24.04 VM
 - Ports **80** and **443** free and reachable from the internet (required for the ACME HTTP-01 challenge)
@@ -34,7 +38,7 @@ ACME_EMAIL=you@example.com
 PROXY_SECRET=<openssl rand -hex 32>
 ALLOWED_CIDR=10.0.0.0/8,172.16.0.0/12
 
-docker-compose up -d
+docker compose up -d
 ```
 
 `DOMAIN` and `ACME_EMAIL` are mandatory — the entrypoint refuses to start without them.
@@ -115,7 +119,7 @@ Arguments: `<url-prefix> <upstream-host> <upstream-path-prefix>`. The third argu
 Update the catch-all hint in the same snippet, then rebuild:
 
 ```bash
-docker-compose up -d --build
+docker compose up -d --build
 ```
 
 ---
@@ -184,10 +188,10 @@ For OpenAI-compatible SDKs set `baseURL` to `https://proxy.bildme.ru/deepseek` a
 
 ```bash
 # Tail logs
-docker-compose logs -f proxy | jq .
+docker compose logs -f proxy | jq .
 
 # Requests per upstream per minute
-docker-compose logs --since=1m proxy --no-log-prefix \
+docker compose logs --since=1m proxy --no-log-prefix \
   | jq -r 'select(.logger=="http.log.access") | .request.uri' \
   | cut -d'/' -f2 \
   | sort | uniq -c | sort -rn