0.2.55 - Remote config/Request fixes

server/README.md

@@ -70,6 +70,11 @@ same order: **who and where** first (`component`, `user`, `device`, `client`), t
 the event is about, with `version` (the gateway build) and `error` last. `MEMBY_LOG_FORMAT`
 switches the whole stream to `logfmt` (slog's own text) or `json` for a collector.
 
+The same structured records are appended to `MEMBY_LOG_HISTORY_PATH` as JSONL and restored
+into the admin log when the gateway starts. Compose mounts that path from the persistent
+`memby-logs` volume, so replacing the container for a new version keeps the previous
+history. The archive is compacted to the configured buffer capacity and remains bounded.
+
 Every line from a request carries the viewer, the television, the app build and the
 `component` — the part of the app the call came from, derived from the route, so it is
 right even for an APK too old to report anything about itself.
@@ -608,7 +613,8 @@ can review and revoke signed-in TVs from the app's Settings screen.
 | `MEMBY_REDIS_URL` | `redis://localhost:6379/0` | |
 | `MEMBY_LISTEN_ADDR` | `:8080` outside Compose; `:32768` in the NAS stack | |
 | `MEMBY_LOG_LEVEL` | `INFO` | Use `DEBUG` for successful probe, status-poll and artwork requests |
-| `MEMBY_LOG_BUFFER_CAPACITY` | `5000` | Bounded in-memory admin event ring; `0` disables capture |
+| `MEMBY_LOG_BUFFER_CAPACITY` | `5000` | Bounded persistent admin event history; `0` disables capture |
+| `MEMBY_LOG_HISTORY_PATH` | `/data/logs/events.jsonl` | JSONL history restored after container replacement |
 | `MEMBY_GOMEMLIMIT` | `384MiB` | Compose value passed to Go as `GOMEMLIMIT` |
 | `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 |