Choose and execute the lyra AI helper stack migration #34

New issue

Open

opened 2026-07-01 18:55:16 +01:00 by nimmo · 0 comments

nimmo commented

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

Owner

Goal

Decide the target shape for the remaining smaller AI-adjacent helper services on lyra and execute the lowest-risk migration path first.

Scope

This issue no longer covers the Wyoming speech stack.

Whisper/Piper native migration now lives in #50.
This issue covers the remaining helper holdouts on lyra, especially services such as Signal CLI REST on 8888 and any other genuinely small AI-adjacent helpers that are still better treated as package-backed custom units or deliberate OCI holdouts.

Acceptance Checklist

Inventory the actual live helper containers and their data/config paths after removing Whisper/Piper from scope.
Classify each remaining helper as native module, package-only custom systemd service, or OCI-wrapper holdout.
Migrate at least one low-state remaining helper service in this pass, or explicitly document why the remaining services should stay on Docker temporarily.
Record which remaining helpers should stay on Docker temporarily and why.
Close this issue only after every service still in scope is either migrated, deliberately retained on Docker with rationale, or moved into a new dedicated issue.

Context

This issue was originally carrying piper and faster-whisper as exploratory helper candidates. That context is now stale: NixOS has first-class Wyoming modules for both, so that migration is tracked separately in #50. The purpose of this issue is now the true remainder set: helper services that still lack strong native coverage or that need custom glue to move off Compose cleanly.

Guardrails

Do not leak tokens, phone credentials, or API secrets into Nix values.
Do not treat unrelated helper services as one inseparable cutover if one of them is clearly ready to split into its own issue.
Do not let this issue become a dumping ground for larger stateful app migrations.

## Goal Decide the target shape for the remaining smaller AI-adjacent helper services on `lyra` and execute the lowest-risk migration path first. ## Scope This issue no longer covers the Wyoming speech stack. - Whisper/Piper native migration now lives in #50. - This issue covers the remaining helper holdouts on `lyra`, especially services such as Signal CLI REST on `8888` and any other genuinely small AI-adjacent helpers that are still better treated as package-backed custom units or deliberate OCI holdouts. ## Acceptance Checklist - Inventory the actual live helper containers and their data/config paths after removing Whisper/Piper from scope. - Classify each remaining helper as native module, package-only custom systemd service, or OCI-wrapper holdout. - Migrate at least one low-state remaining helper service in this pass, or explicitly document why the remaining services should stay on Docker temporarily. - Record which remaining helpers should stay on Docker temporarily and why. - Close this issue only after every service still in scope is either migrated, deliberately retained on Docker with rationale, or moved into a new dedicated issue. ## Context This issue was originally carrying `piper` and `faster-whisper` as exploratory helper candidates. That context is now stale: NixOS has first-class Wyoming modules for both, so that migration is tracked separately in #50. The purpose of this issue is now the true remainder set: helper services that still lack strong native coverage or that need custom glue to move off Compose cleanly. ## Guardrails - Do not leak tokens, phone credentials, or API secrets into Nix values. - Do not treat unrelated helper services as one inseparable cutover if one of them is clearly ready to split into its own issue. - Do not let this issue become a dumping ground for larger stateful app migrations.

nimmo added this to the Lyra Service Stack NixOS Migration milestone

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

nimmo added the

host:lyra

project:lyra-service-stack-migration

labels

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

No milestone

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#34

No description provided.

Rows
Columns