Two fixes: a stray metadata.db no longer stops the container from starting, and your place in the web reader now carries over to KOReader.
docker pull ghcr.io/new-usemame/calibre-web-nextgen:v4.1.32
A stray metadata.db no longer stops the container from starting
Every release since v4.1.20 could refuse to come up if an empty or leftover metadata.db was sitting at the top of your library folder. The log filled with no such table: custom_columns over and over, the app never started, and rolling back to v4.1.19 was the only way out.
NextGen finds your library by looking for that filename, and it had started trusting the first file with that name. A leftover one at the root of /calibre-library got mounted as your library and hid the real one in the folder below it. It now checks that a file is genuinely a Calibre database before mounting it, says in the log which file it skipped and why, and keeps looking. If nothing usable turns up at all it stops with an explanation instead of looping, and it never writes over the files it found.
Where you stopped in the browser carries over to KOReader
Read a few chapters in the web reader, then open the same book on your KOReader device and it moves to roughly where you stopped, instead of resuming where the device itself last was.
It lands near the spot rather than exactly on it. The browser records a position KOReader's engine cannot resolve, so the two share a percentage instead, and it applies when you open the book rather than during a bulk library sync.
This needs the updated NextGen Progress Sync plugin on the device. Until you update it, nothing about its behaviour changes.
Reported by @jrodrigoferreira and kept current by @iroQuai (#1366, #324).
