Developer
dd48214987
Replace the MediaTab and RequestsTab stubs with real implementations on the Jellyfin service page. MediaTab (pages/service-tabs/MediaTab.tsx): lifts the operational content from the top-level Media page into an instance-scoped tab. Build controls, status display, library counts, media DataTable, and pagination all read the Jellyfin service id directly from the instance prop (replacing the old URL-search-param service selector + dropdown). Row-click navigation to the file browser is preserved (note: target /files is a cross-slice dependency on slice 6's FilesTab). RequestsTab (pages/service-tabs/RequestsTab.tsx): reads the absorbed jellyseerr_url + jellyseerr_api_key from the Jellyfin instance config. When unconfigured, renders a CTA to add the fields via the Config tab. When configured, shows the Jellyseerr URL + an honest placeholder (no requests backend endpoint exists yet -- out of scope for this slice). service-tabs/index.ts updated to wire the new components; the MediaTabStub/RequestsTabStub removed from stubs.tsx. Note: this branch is based on main, not on mobile-responsive-parity, so MediaTab lifts main's DataTable + TanStack column-visibility mobile hiding (no MobileCardRow -- that lands when the branches reconcile). Tests: MediaTab (instance-scoped hooks + build controls + table render) + RequestsTab (configured URL vs empty-state CTA). 90 tests pass (+6); lint/build green. Cross-slice flag: MediaTab row-click -> /files will 404 until slice 6 re-routes it to the ssh_tasks FilesTab. Refs openspec/changes/services-as-hub-ia/ (spec R2.4, tasks slice 5).
Manage Frontend
React + TypeScript SPA for Manage, consuming the FastAPI backend.
Tech Stack
- Vite — Build tool
- React 18+ — UI framework
- TypeScript — Type safety
- @tanstack/react-query — Data fetching/caching
- @tanstack/react-table — Data tables (media, file browser)
- react-router-dom — Client-side routing
- Tailwind CSS + shadcn/ui — Styling
Setup
cd frontend
npm install
Development
npm run dev
Runs on http://localhost:5173 with API requests proxied to http://localhost:8000.
Make sure the backend is running:
cd ../backend
uvicorn media_library_viewer_api.main:app --reload --port 8000
Build
npm run build
Output goes to frontend/dist/.
Pages
- Dashboard (
/) — Now playing, library stats, configurable widgets and shortcuts, frontend/backend version chips in the shell header - Observability (
/observability) — Thin dashboard: Alertmanager alerts, Prometheus target health, machine status, and Grafana deep-links (no in-app charting) - Media (
/media) — Full-library table with sort/filter/search - Users (
/users) — Read-only Jellyfin user list with optional Jellyseerr enrichment - File Browser (
/files) — Remote directory browsing, ffprobe preview, jobs - Settings (
/settings) — Persistent monitoring machine definitions, SSH keys, and setup workflow - Actions (
/actions) — Saved server tasks (shell/python) targeting ssh_tasks services
Environment Variables
Set VITE_API_URL and any OIDC variables directly in your shell or Compose build args if the API is not at http://localhost:8000.
The frontend version defaults to the package.json version and can be overridden with VITE_APP_VERSION and VITE_APP_BUILD_INFO when you need explicit deployed labels.
VITE_API_URL=http://your-backend-host:8000
Configuration workflow examples
- Local development: run
docker compose -f docker-compose.dev.yml up --build, then open the app and add monitoring machines in the Settings tab. - Production: export the required Compose variables in your shell, run
docker compose up --build, and manage local/remote machines from Settings. - Observability: Manage only deploys backend + frontend. It connects to existing Grafana/Prometheus/Alertmanager instances; see
docker-compose.observability.ymlfor an optional standalone example stack. A machine can belocal(the API host itself) orssh(a remote host), and the UI treats both the same after configuration.
In development, the Vite proxy handles /api requests automatically. Observability services (Grafana, Prometheus, Alertmanager) are configured in the app on the Services page — there are no observability env vars.