0.2.57 - Traliers bug fixes
This commit is contained in:
+4
-1
@@ -449,7 +449,9 @@ shown, it asks for an Emby household username and password and verifies them dir
|
||||
against Emby. Credentials are never stored. The temporary Emby access token is logged
|
||||
out immediately, and the browser receives a secure, HTTP-only, same-site installer cookie
|
||||
valid for 30 minutes. This browser login does not create a Memby TV session and therefore
|
||||
does not appear in the user's signed-in device list.
|
||||
does not appear in the user's signed-in device list. Emby records the password check
|
||||
under the gateway's own client name (`MEMBY_GATEWAY_CLIENT_NAME`), not a television's, so
|
||||
its temporary device record is never mistaken for a set in the house.
|
||||
|
||||
After authentication, `/updates/latest.apk` redirects to the current immutable, versioned
|
||||
APK in the persistent `memby-releases` volume. Direct APK requests require either that
|
||||
@@ -619,6 +621,7 @@ can review and revoke signed-in TVs from the app's Settings screen.
|
||||
| `MEMBY_SERVER_MEMORY_LIMIT` | `512m` | Compose hard memory ceiling for the server container |
|
||||
| `MEMBY_TIMEZONE` | `Pacific/Auckland` | Local day and time labels for schedule rows |
|
||||
| `MEMBY_CLIENT_NAME` | `MbyATV` | Client name sent to Emby; must match the app's direct path |
|
||||
| `MEMBY_GATEWAY_CLIENT_NAME` | `MbyGateway` | Client name Emby records for the gateway's own requests, including an admin or installer sign-in |
|
||||
| `MEMBY_HOME_TTL` | `60s` | Also `MEMBY_ITEM_TTL`, `MEMBY_SEARCH_TTL`, `MEMBY_SCREENSAVER_TTL` |
|
||||
| `MEMBY_RECOMMEND_TTL` | `24h` | How long computed recommendation rows stay warm |
|
||||
| `MEMBY_RECOMMEND_TIMEOUT` | `60s` | Bounds a background rebuild |
|
||||
|
||||
Reference in New Issue
Block a user