fix: Update Mediamtx Dockerfile and configuration for improved compatibility

Author: 02loveslollipop

media_relay/Dockerfile

@@ -1,5 +1,8 @@
 FROM bluenviron/mediamtx:1.15.3
 
-COPY mediamtx.yaml /mediamtx.yaml
+COPY mediamtx.yml /mediamtx.yml
 
-CMD ["/mediamtx", "/mediamtx.yaml"]
+ENV MTX_CONFIG=/mediamtx.yml
+
+EXPOSE 8554 1935 8888 8889 9998 9999
+EXPOSE 8200/udp

media_relay/README.md

@@ -10,8 +10,8 @@ The container reads the following environment variables that must be configured
 | --- | --- |
 | `RELAY_PUBLISH_USER` | Username the SBC uses while pushing the RTSP stream |
 | `RELAY_PUBLISH_PASS` | Password the SBC uses while pushing the RTSP stream |
-| `RELAY_VIEWER_USER` | Optional username required by frontend clients (leave empty to disable auth) |
-| `RELAY_VIEWER_PASS` | Optional password required by frontend clients (leave empty to disable auth) |
+| `RELAY_VIEWER_USER` | Username required by frontend clients (set to `any` to allow anonymous access) |
+| `RELAY_VIEWER_PASS` | Password required by frontend clients (leave blank when `RELAY_VIEWER_USER=any`) |
 
 If you enable viewer authentication, update the frontend to use the same credentials when negotiating playback.
 
@@ -20,12 +20,12 @@ Ports exposed by the container:
 - `8554/tcp`: RTSP ingest from the SBC
 - `1935/tcp`: RTMP ingest (alternative to RTSP)
 - `8888/tcp`: HTTP server (HLS playback and API)
-- `8889/tcp` plus `UDP 8200-8299`: WebRTC signalling and media
+- `8889/tcp` plus `8200/udp`: WebRTC signalling and media
 - `9998/tcp`: Prometheus metrics (optional)
 - `9999/tcp`: pprof endpoint (optional)
 
 Ensure the Elastic Beanstalk load balancer and security groups forward the required ports. For WebRTC, terminate TLS at the load balancer and forward HTTPS traffic to port `8889`.
 
 ## Deployment bundle
 
-The GitHub Actions workflow zips the contents of this folder and uploads the archive as an application version. The Dockerfile simply copies the Mediamtx configuration and launches the server binary.
+The GitHub Actions workflow zips the contents of this folder and uploads the archive as an application version. The Dockerfile copies `mediamtx.yml` into the image and relies on the Mediamtx entrypoint to launch the server.

media_relay/mediamtx.yaml

@@ -0,0 +1,53 @@
+logLevel: info
+
+authMethod: internal
+authInternalUsers:
+  - user: ${RELAY_PUBLISH_USER}
+    pass: ${RELAY_PUBLISH_PASS}
+    permissions:
+      - action: publish
+        path: robot
+  - user: ${RELAY_VIEWER_USER}
+    pass: ${RELAY_VIEWER_PASS}
+    permissions:
+      - action: read
+        path: robot
+      - action: playback
+        path: robot
+  - user: any
+    pass:
+    ips: ['127.0.0.1', '::1']
+    permissions:
+      - action: api
+      - action: metrics
+      - action: pprof
+
+rtsp: yes
+rtspAddress: :8554
+
+rtmp: yes
+rtmpAddress: :1935
+
+hls: yes
+hlsAddress: :8888
+hlsVariant: lowLatency
+hlsSegmentDuration: 1s
+hlsPartDuration: 200ms
+
+webrtc: yes
+webrtcAddress: :8889
+webrtcAllowOrigin: '*'
+webrtcLocalUDPAddress: :8200
+webrtcICEServers2:
+  - url: stun:stun.l.google.com:19302
+
+metrics: yes
+metricsAddress: :9998
+
+pprof: yes
+pprofAddress: :9999
+
+paths:
+  robot:
+    source: publisher
+    overridePublisher: yes