/claim #4

Summary

• Add a same-origin Next.js proxy at /api/mediamtx/[...path] so browser login checks can reach MediaMTX through the dashboard server instead of calling Docker-only hostnames directly.
• Normalize legacy API base URLs that end in /v3 or /v3/config, preventing duplicated paths like /v3/config/v3/config/global/get.
• Update Docker defaults, compose files, env examples, and docs to use /api/mediamtx publicly and MEDIAMTX_API_URL internally.
• Expand nginx API proxying from /v3/config/ to the full /v3/ API surface and handle auth-bearing CORS preflight requests.

Why this fixes the Docker login

The default credentials are valid in mediamtx.yml, but Docker builds could expose either http://mediamtx:9997 to the browser or an API URL that already included /v3/config. The browser cannot resolve the Docker service hostname, and the old /v3/config default caused the login request to target the wrong path once the app appended /v3/config/global/get.

Verification

• pnpm test
• pnpm lint
• pnpm exec tsc --noEmit
• pnpm build