Migrate Jellyfin on lyra back to the native NixOS service #30

New issue

Open

opened 2026-07-01 18:53:17 +01:00 by nimmo · 0 comments

nimmo commented

2026-07-01 18:53:17 +01:00

Owner

Goal

Revisit the earlier Jellyfin migration on lyra and complete it as a native NixOS service without repeating the mount and state-handling mistakes that led to the Docker reversion.

Acceptance Checklist

Reconstruct the current Jellyfin Docker layout and the intended host paths.
Define the NAS-backed mounts declaratively before touching Jellyfin itself.
Move Jellyfin config, cache, and metadata into a NixOS-managed path.
Configure hardware acceleration explicitly for the RTX 4070 path that lyra actually uses.
Cut over the reverse-proxy target only after the native service is healthy.
Keep a short rollback window where the Docker stack can be brought back quickly.

Context

This host previously had a native Jellyfin attempt that was later reverted in favour of Docker. The issue is not whether NixOS can run Jellyfin; it can. The real risk is the network-backed storage and GPU wiring around it.

Guardrails

Do not start by rewriting the app config in Nix if the existing UI-managed state is still acceptable.
Do not treat the old reversion as proof that Jellyfin should stay on Docker forever; treat it as evidence that the mount design must be settled first.
Validate playback, library visibility, and at least one hardware-transcoded stream before decommissioning the container.

## Goal Revisit the earlier Jellyfin migration on `lyra` and complete it as a native NixOS service without repeating the mount and state-handling mistakes that led to the Docker reversion. ## Acceptance Checklist - Reconstruct the current Jellyfin Docker layout and the intended host paths. - Define the NAS-backed mounts declaratively before touching Jellyfin itself. - Move Jellyfin config, cache, and metadata into a NixOS-managed path. - Configure hardware acceleration explicitly for the RTX 4070 path that `lyra` actually uses. - Cut over the reverse-proxy target only after the native service is healthy. - Keep a short rollback window where the Docker stack can be brought back quickly. ## Context This host previously had a native Jellyfin attempt that was later reverted in favour of Docker. The issue is not whether NixOS can run Jellyfin; it can. The real risk is the network-backed storage and GPU wiring around it. ## Guardrails - Do not start by rewriting the app config in Nix if the existing UI-managed state is still acceptable. - Do not treat the old reversion as proof that Jellyfin should stay on Docker forever; treat it as evidence that the mount design must be settled first. - Validate playback, library visibility, and at least one hardware-transcoded stream before decommissioning the container.

nimmo changed title from ~~placeholder~~ to Migrate Jellyfin on lyra back to the native NixOS service

2026-07-01 18:54:59 +01:00

nimmo added this to the Lyra Service Stack NixOS Migration milestone

2026-07-01 18:54:59 +01:00

nimmo added the

host:lyra

project:lyra-service-stack-migration

labels

2026-07-01 18:55:41 +01:00