View Single Post
Old 05-19-2017, 12:19 AM   #254
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by kovidgoyal View Post
Oh well, I decided to implement this, turns out to not be too hard as there was already existing code for it (originally I intended the new server to have the same restriction capability as the old server). Will be in the next beta release.
Thanks.

Although it looks like you haven't wired this up to calibre-server --manage-users yet.

Speaking of which, I was able to use the CLI for that while calibre was running (in fact, while I was looking at the Preferences UI for managing calibre-server users).
I guess this is exempt because it only touches the user database and it reads directly from there rather than running a potentially-conflicting in-memory copy?
eschwartz is offline   Reply With Quote