Fix storage path nesting for data migration #2

Merged

backmeupplz merged 1 commit from data-migration into master

2026-03-02 14:26:19 +00:00

backmeupplz commented

2026-03-02 14:25:23 +00:00

(Migrated from github.com)

Summary

Remove myground/{instance_id}/ prefix from storage paths when user provides a custom storage path during service install
Single-volume services (e.g. Navidrome) use the user's path directly
Multi-volume services (e.g. Immich) use {path}/{volume_name}/ subdirectories
Lets users point at existing data directories and have services pick up where they left off — no separate "adopt" flow needed

Test plan

Install a single-volume service (navidrome) with custom storage path, verify data goes to the path directly (no nesting)
Install a multi-volume service (immich) with custom storage path, verify subdirectories are created per volume
Point a fresh install at an existing data directory, verify service picks up existing data
All 171 tests pass (107 unit + 6 main + 58 integration)

🤖 Generated with Claude Code

## Summary - Remove `myground/{instance_id}/` prefix from storage paths when user provides a custom storage path during service install - Single-volume services (e.g. Navidrome) use the user's path directly - Multi-volume services (e.g. Immich) use `{path}/{volume_name}/` subdirectories - Lets users point at existing data directories and have services pick up where they left off — no separate "adopt" flow needed ## Test plan - [ ] Install a single-volume service (navidrome) with custom storage path, verify data goes to the path directly (no nesting) - [ ] Install a multi-volume service (immich) with custom storage path, verify subdirectories are created per volume - [ ] Point a fresh install at an existing data directory, verify service picks up existing data - [ ] All 171 tests pass (107 unit + 6 main + 58 integration) 🤖 Generated with [Claude Code](https://claude.com/claude-code)