Fix Navidrome automatic library scan schedule #101

Merged
eblume merged 1 commit from fix/navidrome-scan-schedule into main 2026-02-04 07:23:12 -08:00
Owner

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

## 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)
The env var ND_SCANSCHEDULE was incorrect - Navidrome uses viper config
with dots replaced by underscores, so scanner.schedule becomes
ND_SCANNER_SCHEDULE. Also explicitly use @every format for clarity.

Also reorders CLAUDE.md rules to emphasize running zk-docs first.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
eblume merged commit 1e13d4b83d into main 2026-02-04 07:23:12 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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
eblume/blumeops!101
No description provided.