0.2.65 - End Credits wiring / Gateway: 0.1.45 - Credits

.env.example

@@ -7,6 +7,20 @@ MEMBY_EMBY_URL=https://molise.bounceme.net
 # above — video goes device -> Emby directly, never through the gateway.
 MEMBY_EMBY_PUBLIC_URL=https://molise.bounceme.net
 
+# Where the gateway reads media *bytes* from, which is a different question from the two
+# addresses above and matters for exactly one subsystem.
+#
+# Credits detection is the only server-side thing that opens a media file, and it does so as
+# ranged reads over the last few minutes of it. The gateway runs on the NAS (10.0.0.213) and
+# the media and Emby live on the HTPC (10.0.0.2), so with this unset every one of those
+# ranged reads takes MEMBY_EMBY_URL: out to the DDNS name, through TLS and the reverse proxy,
+# and back in — and a proxy that buffers turns the ranged read into a whole-file read, which
+# is the one thing the scan design exists to avoid.
+#
+# Unset, it falls back to MEMBY_EMBY_URL and behaves exactly as before. Confirm the port your
+# Emby listens on over plain HTTP on the LAN before uncommenting.
+#MEMBY_EMBY_MEDIA_URL=http://10.0.0.2:8096
+
 # Postgres password for the memby role. Generate one, e.g.
 #   openssl rand -base64 24
 POSTGRES_PASSWORD=7dfc3eb07108013c7bea9787457397551b5eb9059adac51aea4741f4ec649be2