YoursFunny 36e5e8afe6 chore(log): cap container log growth and echo the resolved config ...

P2 of the logging plan (the README recipe landed with the code change):

- `docker-compose.yml.example`: one `x-logging` anchor applied to all three
  services. json-file grows without limit by default, so a long-running bot
  and the proxy in front of it fill the disk; capped at 10m × 3 files.
- The startup `config:` line now reports what the process actually resolved —
  the state DB path (a mistyped `DATA_DIR` or a surprising CWD was invisible
  until it bit), both TTLs, the caption-quote setting (`off` rather than a bare
  `0`) and whether a proxy is configured. The proxy URL is never printed (it
  may embed credentials) and admin ids — chat identifiers — stay at `debug`.

Verified: `docker compose config -q` accepts the file, and a scripted fake-API
run shows `caption quote off` / `link cache TTL 3600s` under overrides,
`proxy=yes` with no credential in any line, and the ids at `debug` only.

2026-09-20 19:14:33 +08:00

..

x-media

feat(log): survive a bare deployment and name what each line is about

2026-09-20 19:07:23 +08:00

xmedia-bot

chore(log): cap container log growth and echo the resolved config

2026-09-20 19:14:33 +08:00