[eschwartz]

Originally Posted by Mex5150

That's great news, I was rather concerned (I remember having problems with two instances of the GUI accessing the same library on a network drive in an early experiment years ago).

The CLI server never writes to the library, so it is always safe.
(Well, if the database schema is upgraded then the CLI server will perform that update...)

I know it's concidered a cardinal sin in the Calibre community, but multiple libraries makes accessing the files directly outside of Calibre a lot easier too, so no plans to change.

Not a cardinal sin, but you should know why you chose to do so, and make up your own mind whether it makes sense to use Virtual Libraries instead.

I make extensive use of both VLs and multiple physical libraries.

I know this is probably a 'how long is a piece of string?' question, but any idea on when that may be? I have nothing really urgent to serve, so waiting a week or two for the new version is fine, but if it's going to be a few months, I'll just get on with the multiple CLI versions in the meantime ;^>


~Mex

Just go with multiple CLI incantations.

When calibre v.30 comes out, you can upgrade your startup routine.
Multiple CLI invocations aren't really a bad thing, honestly... as I said, it's pretty lightweight, so why not?


Also, what distro do you use (I use ArchLinux), and does it use systemd as its init system?
Here is a systemd unit file which starts up a calibre library via drop-in config files.

[eschwartz@arch ~]$ cat ~/.config/systemd/user/calibre-server@.service
[Unit]
Description=Main calibre server
After=network.target

[Service]
EnvironmentFile=/%h/.config/calibre/servers/%i.conf
ExecStart=/usr/bin/calibre-server \
    --port "${port}" \
    --with-library "${path}" \
    --restriction "${restriction}" \
    --user "${user}" \
    --pass "${pass}"

[Install]
WantedBy=default.target

In your calibre configuration directory, create a folder called "servers", add ${library_name}.conf files, and keep the various parameters in the conf file.

[eschwartz@arch ~]$ cat ~/.config/calibre/servers/amazon.conf
port=""
path="/home/eschwartz/Calibre Libraries/Amazon"
restriction=""
user=""
pass=""

Then start a library with

systemctl --user start calibre-server@libraryname

or enable it every time you login with

systemctl --user enable calibre-server@libraryname

...

When will the new server be available? I don't know.
The rewrite started in May-June (basic infrastructure), took a siesta until October (another tool needed was being worked on outside of calibre's codebase), and you can see the current progress using

calibre-debug --new-server

As you can see there is still a ways to go. It's being rewritten from the ground up. I would go with a few months.
Hey, we have a partially working demo.

I just stick with "exciting things are ahead".