fix: make local development work out of the box

- library.example.yaml now uses relative ./media paths for local runs
- clearer startup errors for missing roots and config files
- ignore the local config/library.yaml override
This commit is contained in:
TapTap committed 2026-11-13 12:12:17 +00:00
1 parent f5e247e164
commit af2a8bd35d
5 files changed
+31 -11

No files matched your search

+6 -4
View File
@@ -25,18 +25,20 @@ mkdir -p media/music media/longform
library:
folders:
- id: 1
name: "Alice - Music"
name: "Music"
type: music
path: /absolute/path/to/music/alice
path: ./media/music
- id: 10
name: "Audiobooks & Podcasts"
type: longform
path: /absolute/path/to/longform
path: ./media/longform
```
The example file already uses these relative paths, so no edit is needed for local development. Relative paths are resolved from the working directory (`./gradlew run` uses the project root). For deployment, replace them with absolute paths such as `/mnt/media/music/alice` (see Section 6.1).
- `type: music` roots are assigned per user; `type: longform` roots are shared with every user.
- `id` must be stable and unique (integers). It is part of song IDs, so do not renumber it after a scan.
- Paths must exist and be readable, otherwise the server refuses to start.
- Paths must exist and be readable, otherwise the server refuses to start with a clear error naming the folder.
### 3. Configure users