now supports multi machine monitoring

README.md

@@ -21,7 +21,8 @@ The project consists of two subprojects:
 ## Features
 
 - Dashboard with now-playing sessions, server monitoring overview, and per-library media counts
-- Server monitoring with CPU, IO wait, RAM, network, and disk I/O charts
+- Server monitoring with CPU, IO wait, RAM, network, and disk I/O charts plus a sortable dashboard table covering all configured machines
+- Per-machine monitoring settings with local and remote targets managed in the UI, plus backend-collected recent action history per machine
 - SQLite-indexed media table with full-library sort/filter
 - Read-only Users tab with Jellyfin as the base source and optional Jellyseerr enrichment
 - Remote file browser with ffprobe preview and job execution
@@ -32,7 +33,7 @@ The project consists of two subprojects:
 
 ### Docker Compose (recommended)
 
-Production-style deployment with the frontend serving the SPA and proxying `/api` to the backend:
+Production-style deployment with the frontend serving the SPA and proxying `/api` to the backend. The compose files rely on environment-variable interpolation, so export the required values in your shell before running them (no `env_file` is needed):
 
 ```bash
 docker compose up --build
@@ -48,6 +49,7 @@ docker compose -f docker-compose.dev.yml up --build
 
 Frontend runs on http://localhost:5173 and the backend on http://localhost:8000.
 The backend media index is persisted in a Docker volume (`backend_cache`) so rebuilds and container restarts do not force a full re-index.
+Monitoring machine definitions and recent machine activity are stored in the backend so the UI can show one section per configured machine and preserve history across restarts.
 
 ### Manual backend/frontend development
 
@@ -67,7 +69,37 @@ npm run dev
 
 ## Configuration
 
-Create a `.env` file in the project root:
+The Compose files use environment-variable interpolation. Export the required variables in your shell or pass them inline; a `.env` file is optional, not required.
+
+### Compose examples
+
+Production-style example with shell exports:
+
+```bash
+export JELLYFIN_URL=https://jellyfin.example.com
+export JELLYFIN_API_KEY=your-api-key
+export SSH_HOST=media-server.example.com
+export SSH_USERNAME=username
+export SSH_KEY_HOST_DIR=$HOME/.ssh
+export SSH_KEY_NAME=id_ed25519
+export BACKEND_APP_HOST=manage.example.com
+export FRONTEND_APP_HOST=manage.example.com
+export CERT_RESOLVER=letsencrypt
+export VITE_OIDC_ISSUER=https://authentik.example/application/o/manage/
+export VITE_OIDC_CLIENT_ID=manage
+export VITE_OIDC_REDIRECT_URI=https://manage.example.com/
+export VITE_OIDC_POST_LOGOUT_REDIRECT_URI=https://manage.example.com/
+
+docker compose up --build
+```
+
+Inline one-liner example:
+
+```bash
+JELLYFIN_URL=https://jellyfin.example.com JELLYFIN_API_KEY=your-api-key SSH_HOST=media-server.example.com SSH_USERNAME=username SSH_KEY_HOST_DIR=$HOME/.ssh SSH_KEY_NAME=id_ed25519 BACKEND_APP_HOST=manage.example.com FRONTEND_APP_HOST=manage.example.com CERT_RESOLVER=letsencrypt VITE_OIDC_ISSUER=https://authentik.example/application/o/manage/ VITE_OIDC_CLIENT_ID=manage VITE_OIDC_REDIRECT_URI=https://manage.example.com/ VITE_OIDC_POST_LOGOUT_REDIRECT_URI=https://manage.example.com/ docker compose up --build
+```
+
+Example environment variables:
 
 ```bash
 JELLYFIN_URL=https://jellyfin.example.com
@@ -140,4 +172,4 @@ cd frontend && npx tsc --noEmit && npm run build
 - SSH commands run through `/bin/sh -c` regardless of remote login shell.
 - Job templates are shell-quoted. Add new templates in `backend/src/media_library_viewer_api/jobs.py`.
 - Monitoring collector uses JSONL in `/tmp`, pruned to 7 days / 70k lines.
-- Root-level Docker Compose files are provided for production (`docker-compose.yml`) and local development (`docker-compose.dev.yml`).
+- Root-level Docker Compose files are provided for production (`docker-compose.yml`) and local development (`docker-compose.dev.yml`), and both rely on Compose interpolation rather than `env_file` entries.