sstent/navidrome-litefs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

conductor(plan): Mark phase 'Infrastructure Configuration Update' as complete

Browse Source
This commit is contained in:
sstent
2026-02-07 17:52:26 -08:00
parent 5a5790205b
commit 8568f4e9b9
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
conductor/tracks/fix_routing_20260207/plan.md
View File

@@ -2,14 +2,14 @@
This plan outlines the steps to reconfigure the Navidrome-LiteFS cluster to bypass the LiteFS write-forwarding proxy and use direct primary node routing for improved reliability and performance.
## Phase 1: Infrastructure Configuration Update
## Phase 1: Infrastructure Configuration Update [checkpoint: 5a57902]
In this phase, we will modify the Nomad job and LiteFS configuration to support direct port access and primary-aware health checks.
- [ ] Task: Update `navidrome-litefs-v2.nomad` to point service directly to Navidrome port
- [ ] Modify `service` block to use port 4533 instead of dynamic mapped port.
- [ ] Replace HTTP health check with a script check running `litefs is-primary`.
- [ ] Task: Update `litefs.yml` to ensure consistent internal API binding (if needed)
- [ ] Task: Conductor - User Manual Verification 'Infrastructure Configuration Update' (Protocol in workflow.md)
- [x] Task: Update `navidrome-litefs-v2.nomad` to point service directly to Navidrome port
- [x] Modify `service` block to use port 4533 instead of dynamic mapped port.
- [x] Replace HTTP health check with a script check running `litefs is-primary`.
- [x] Task: Update `litefs.yml` to ensure consistent internal API binding (if needed)
- [x] Task: Conductor - User Manual Verification 'Infrastructure Configuration Update' (Protocol in workflow.md)
## Phase 2: Deployment and Validation
In this phase, we will deploy the changes and verify that the cluster correctly handles primary election and routing.