splitsec2
20848a8774
These are the leftovers from the docs check, the fixes that did not belong in the other three. Claude did the comparison and wrote the changes here too, so I would still like a human look before it merges. The one new piece of prose worth a read is `troubleshooting.md`. It was a TODO page that two other pages link to, so I filled it with only what I could confirm in the code: where the logs go, `LOG_LEVEL`, the `DEBUG=true` bundle from the bug report template, and reporting an issue. Happy to drop it back to a stub if you would rather write that one yourself. - `configuration.md`, `custom-scripts.md`, `users-and-requests.md`: Booklore is Grimmory in the UI now. The stored mode value is still `booklore`, and the custom script doc says so. The hardlink heading now matches the "Hardlink Book Torrents" and "Hardlink Audiobook Torrents" checkboxes. - `custom-scripts.md`: the email output runs scripts too (`phase=post_email`, `output.mode=email`, details under `output.details.email`). It was missing from the phase list. - `users-and-requests.md`: a delivery that fails with no retry available goes back to pending on its own, and the admin reopen action is for rejected requests. The page said an admin reopens a failed delivery. Also noted that rules cannot use Request Book. - `hardcover-sync.md`: added the missing `AUTO_DOWNLOAD_AUDIOBOOK_MIN_SIZE_PERCENT` row and a sentence in the ranking paragraph. - `api-access.md`: an admin session also reads `/api/stats`, and what the 403 says. - `installation.md`: points at the Lite, Tor and WireGuard variants. Docs only, no code touched.
1.1 KiB
Troubleshooting
Start with the logs, then attach a debug bundle if you open an issue.
Logs
Shelfmark writes its log to the container output, so docker logs shelfmark shows it. With ENABLE_LOGGING on (the default) it also writes log files under LOG_ROOT/shelfmark/ (/var/log/shelfmark/ by default), including shelfmark.log and the startup logs.
LOG_LEVEL sets how much is written (INFO by default). Set it to DEBUG to see what a search or download is doing. See the Environment Variables reference for both settings.
Debug bundle
Set DEBUG=true on the container and restart it. A DEBUG button then appears in the interface. It generates a zip with logs, configuration and environment details, with sensitive values redacted. Have a look through it before you post it publicly, then attach it when you open an issue.
Reporting an issue
Open an issue on GitHub and fill in the bug report template. A description of what you expected, the steps to reproduce it and the debug bundle are what make a problem findable.