Migrate Stash on lyra to the native NixOS service #33

Open
opened 2026-07-01 18:55:11 +01:00 by nimmo · 0 comments
Owner

Goal

Replace the Docker-based Stash deployment on lyra with the native NixOS Stash service.

Acceptance Checklist

  • Confirm the current Stash bind mounts, database location, and media-library paths.
  • Define the target host data path for the native service.
  • Decide whether Stash config should remain UI-mutable or become declarative over time.
  • Configure the native service to preserve the current access pattern on port 9999, or consciously retarget it.
  • Validate library scans, metadata writes, and any configured Stash Box integrations before retiring the container.

Context

services.stash now exists in nixpkgs, which makes this a better migration candidate than fully custom services. The likely complexity is the NFS-backed media layout and any accumulated app state.

Guardrails

  • Do not force full declarative settings on day one if that makes the cutover riskier.
  • Validate auth and public-exposure assumptions explicitly if the current reverse-proxy path changes.
## Goal Replace the Docker-based Stash deployment on `lyra` with the native NixOS Stash service. ## Acceptance Checklist - Confirm the current Stash bind mounts, database location, and media-library paths. - Define the target host data path for the native service. - Decide whether Stash config should remain UI-mutable or become declarative over time. - Configure the native service to preserve the current access pattern on port `9999`, or consciously retarget it. - Validate library scans, metadata writes, and any configured Stash Box integrations before retiring the container. ## Context `services.stash` now exists in nixpkgs, which makes this a better migration candidate than fully custom services. The likely complexity is the NFS-backed media layout and any accumulated app state. ## Guardrails - Do not force full declarative settings on day one if that makes the cutover riskier. - Validate auth and public-exposure assumptions explicitly if the current reverse-proxy path changes.
Sign in to join this conversation.
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
nimmo/nixos-config#33
No description provided.