|
Hi Kovid, I have to agree with the others in this thread. For me, it is a regression that I cannot start calibre anymore when calibre-server is running.
To to me the whole point of calibre-server is that I can easily access my library from my (android) devices (eg CalibreCompanion, which I bought), without having to worry about starting anything on the server.
On the other hand, whenever I want to manipulate my library (add books/...), I should not have to "sudo systemctl stop calibre-server.service". And then later having to remember to "sudo systemctl start calibre-server.service". It seriously impacts usability.
Please reconsider this change, or at least implement a "read-only" mode for calibre-server. I would guess that most people use calibre-server the same way as I do: for read-only access to the library. For that group of users, the current behavior is just to onerous.
Other than that, keep up the good work!
|