Fix Navidrome automatic library scan schedule (#101)
## Summary - Fix env var name from `ND_SCANSCHEDULE` to `ND_SCANNER_SCHEDULE` (Navidrome uses viper config where dots become underscores) - Use explicit `@every 1h` format for clarity - Reorder CLAUDE.md rules to emphasize running zk-docs first ## Root Cause Navidrome logs showed "Periodic scan is DISABLED" at startup despite the env var being set. The config key is `scanner.schedule`, which translates to `ND_SCANNER_SCHEDULE` (not `ND_SCANSCHEDULE`). ## Deployment and Testing - [ ] Sync navidrome app: `argocd app sync navidrome` - [ ] Verify pod restarts with new env var - [ ] Check logs for "Scheduling scanner" message instead of "Periodic scan is DISABLED" - [ ] Wait ~1 hour and confirm scan runs automatically 🤖 Generated with [Claude Code](https://claude.ai/code) Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/101
This commit is contained in:
parent
72f9f21d46
commit
1e13d4b83d
3 changed files with 7 additions and 5 deletions
1
docs/changelog.d/fix-navidrome-scan-schedule.bugfix.md
Normal file
1
docs/changelog.d/fix-navidrome-scan-schedule.bugfix.md
Normal file
|
|
@ -0,0 +1 @@
|
|||
Fix Navidrome automatic library scan by correcting env var name from `ND_SCANSCHEDULE` to `ND_SCANNER_SCHEDULE`
|
||||
Loading…
Add table
Add a link
Reference in a new issue