Give Emby a dedicated LAN address

servers/unraid/emby/README.md

@@ -4,13 +4,13 @@ Arcane Git Sync deployment for the official Emby Server image.
 
 ## Endpoint
 
-- Web setup: `http://192.168.50.100:8097`
-- Container HTTP port: `8096/tcp`
+- Web setup: `http://192.168.50.12:8096`
+- Dedicated LAN address: `192.168.50.12/24` on external Docker network `br0`
 
-Jellyfin already owns the default Emby/Jellyfin ports on this host, so this
-project intentionally does not publish `8920/tcp`, `7359/udp`, or `1900/udp`.
-Clients should add the server manually by URL when automatic LAN discovery is
-not available.
+Jellyfin owns the default Emby/Jellyfin ports on the unRaid host address. Emby
+therefore has its own macvlan address on `br0`, where it can use the native
+`8096/tcp`, `8920/tcp`, `7359/udp`, and `1900/udp` ports without host port
+mapping conflicts. Reserve or exclude `192.168.50.12` in the UDM DHCP scope.
 
 ## Persistent data
 

servers/unraid/emby/compose.yaml

@@ -8,8 +8,9 @@ services:
       GID: "100"
       GIDLIST: "100"
       TZ: Asia/Shanghai
-    ports:
-      - "8097:8096/tcp"
+    networks:
+      br0:
+        ipv4_address: 192.168.50.12
     volumes:
       - /mnt/user/appdata/EmbyServer/config:/config
       - /mnt/user/appdata/EmbyServer/transcode:/transcode
@@ -26,3 +27,7 @@ services:
         max-size: 10m
         max-file: "3"
 
+networks:
+  br0:
+    external: true
+    name: br0