Record the search index rebuild schedule in the plan

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-09 15:14:07 -08:00
co-authored by Claude Opus 5.5
parent 695f8d009f
commit 3a32008ed6
+5 -3
View File
@@ -785,9 +785,11 @@ scores with the same split by source as the local check. The profile's score
search then returned 500, for any search: the Lucene song and player indexes search then returned 500, for any search: the Lucene song and player indexes
were written next to the DLL in the read-only `/nix/store` (phase 2 step 6 were written next to the DLL in the read-only `/nix/store` (phase 2 step 6
had planned to move them). Server `2631c46` adds `SearchIndexPath` had planned to move them). Server `2631c46` adds `SearchIndexPath`
(MirrorMode, set to `/var/lib/plebleader/search`); nix-pleb bumps it. The (MirrorMode, set to `/var/lib/plebleader/search`). Server `81f12ee` then
index rebuilds 2 s after the API starts and then every 6 h, so songs a sync moved the rebuild into the importer: it replaces the indexes at the end of a
adds become searchable at the next rebuild. The next `plebleader-sync` run that added scores (so at most once a day, right after the sync), or when
there are none. The API builds them only when missing; upstream appended every
song again every 6 h. nix-pleb `bcdd591`, `a313f5b` bump both. The next `plebleader-sync`
run re-imports with the merge. run re-imports with the merge.
ScoreSaber scores become BeatLeader `Score` rows, and each leaderboard keeps ScoreSaber scores become BeatLeader `Score` rows, and each leaderboard keeps