Choose and execute the next native-module migration after SABnzbd #27
Labels
No labels
host:electra
host:fleet
host:lyra
host:vega
host:vega
phase:cutover
phase:deploy
phase:mcp
phase:module
phase:packaging
phase:prep
phase:validation
project:attic-postgres-lyra-rollout
project:auto-update-reliability
project:declarative-purity-cleanup
project:external-review
project:host-facts-refactor
project:lyra-nixos-deploy
project:lyra-service-stack-migration
project:nebula-mesh-network
project:security-hardening
project:service-stack-migration
project:vega-sillytavern-cutover
service:auto-update
service:mem0
service:sillytavern
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
nimmo/nixos-config#27
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Pick the next high-value native-module migration after SABnzbd and execute it with the real trade-offs documented.
Context
The note ranks
tdarrandwhisparr-v3as the next serious candidates after SABnzbd. Both have native module coverage, but the operational risks differ.Acceptance Checklist
tdarrorwhisparr-v3is the lower-risk next migration.Trade-off Framing From The Note
tdarr: device and storage wiring complexity (/dev/dri, NFS, CIFS, external server dependency)whisparr-v3: app-state and multi-instance complexity (whisparr-v2,whisparr-v3,autobrr, shared media/appdata)Notes
This issue exists so the roadmap has an explicit decision point rather than silently stalling after SABnzbd.