Fix broken default compose: revert to single service + add host-mode overlay

[queueeee]

Why

PR #15 broke the default docker compose up -d workflow: I put profiles: ["", "bridge"] on the bot service thinking the empty-string profile would match "no profile flag", but in Compose semantics it's just an explicit profile named "". So plain docker compose up -d activated nothing → no logs, no service, user had to ask "wo sind meine logs".

Fix

Roll back to a single-service docker-compose.yml (identical to pre-#15 behaviour). For host-network mode, layer a docker-compose.host.yml overlay via -f:

# Default bridge (original behaviour, unchanged)
docker compose up -d

# Host networking (works around docker-bridge ICE failures)
docker compose -f docker-compose.yml -f docker-compose.host.yml up -d

The overlay uses Compose v2's !reset null to drop the bridge attachment, the ts6-net network section, and the 127.0.0.1:8080 port mapping; then network_mode: host joins the host namespace.

Test plan

• ruff check src tests — clean
• pytest — 219 passed
• Live: plain docker compose up -d works again (gets logs).
• Live: docker compose -f docker-compose.yml -f docker-compose.host.yml up -d puts the bot in host net mode (ICE then has real LAN/WAN candidates).

Operator commands (recovery)

cd /opt/ts6-stream-bot
git pull
docker compose down
docker compose up -d                          # back to logging working
docker compose logs -f

When you're ready to try host networking:

# .env: TS6_HOST=127.0.0.1 (oder Host-IP, weil "teamspeak-server" nur im docker-Netz auflöst)
nano .env
docker compose down
docker compose -f docker-compose.yml -f docker-compose.host.yml up -d
docker compose logs -f

https://claude.ai/code/session_016DuCjRJK995Tj9aDhhB9at

---

Generated by Claude Code