How to restrict anonymous user access?

[martianrock]

Hi, I am trying to restrict anonymous access to a specific tag or vl, my web search found --restrictions CLI option but it does not seem to be available in recent version of calibre-server. Is there alternative to --restrictions now?
tl;dr
I was planning (after reading about --restrictions option) to run 2 instances, one read-only no auth on port 80 restricted to tag:ready (i.e. 'ready' server) and another one with auth but unrestricted on default port 8080 ('staging/work in progress' server). And I was planning to run them both from the same library directory (with one of them being read-only I figured it wound not have write conflicts).
If that setup is not possible, would it be possible to have a sync script which would copy only stuff tagged with tag:ready or vl:ready to another library?

[kovidgoyal]

You can define restrictions per user in the modern server. There arent restrictions for anonymous users.

[martianrock]

Originally Posted by kovidgoyal

You can define restrictions per user in the modern server. There arent restrictions for anonymous users.

That's unfortunate, I'd think anonymous users would require more restrictions than authenticated ones. Thanks for confirming it!
Is there by any chance a way to copy library and filter it out by tag in on server side (without calibre UI)?

[martianrock]

Originally Posted by martianrock

That's unfortunate, I'd think anonymous users would require more restrictions than authenticated ones. Thanks for confirming it!
Is there by any chance a way to copy library and filter it out by tag in on server side (without calibre UI)?

I guess I can craft something with calibredb list --search filter and calibredb export. or filesystem copy and calibredb list --search followed by calibredb remove. But if there's a better solution, that'd be great to know.

[kovidgoyal]

You cant have both anonymous and non-anonymous access. If you want anonymous access, then simply create a special library and expose it. If you want authenticated access then define restirctions per user.

[martianrock]

Originally Posted by kovidgoyal

You cant have both anonymous and non-anonymous access. If you want anonymous access, then simply create a special library and expose it. If you want authenticated access then define restirctions per user.

That's what I am trying to achieve by having 2 separate libraries and copying from 'staging' library to 'prod' library with filtering by tags, so that only books with special tag are copied. I want to automate it via cron script or something like that so I'd only have to tag a book as 'ready' in my 'staging' (authenticated) instance on port 8080 and it would (eventually) end up in my anonymous and read-only instance on port 80.