thraxis

They've added volumes to the docker now... the template is broken again.

@fuzzewuzze LL operates in two modes. 1. LL creates and manages the library 2. LL works in conjunction with Calibre and looks at a Calibre library This docker presumes the second case. To solve your issue. 1. Empty your /books/Calibre directory completely 2. Use the windows app to Switch / Create library select that folder and create a new library so it will generate a metadata.db file for calibredb in the docker to access As you evidently did create a metadata.db using the terminal with "/opt/calibre/calibredb add /books/Calibre/* --library_path books/Calibre/ -r " any books downloaded after that point should import using calibredb correctly in the future. IF you have your LL config set to use "/opt/calibre/calibredb" as the calibre import program.

To use the Content Server with RDP-Calibre goto preferences -> Sharing overt the net. enable "Requre username and password" and "Run server automatically" then "Start Server" Create a user and make sure they have write access Check your Docker Settings to see what IP and port you used for the :8081 port mapping. Goto Lazy Librarian and setup the Calibre Settings to use the Content Server. Now when Lazy Librarian processes a book it will use the RDP-Calibre to do so, which will automatically update the book list to include the new book.

The issue you have described is expected behavior. Calibre (ie RDP-Calibre) loads calibre library database when it starts and does NOT monitor for changes made by other Calibre instances (LL-Calibre) that directly access the Calibre Library. To do what you would like you would need to setup Calibre as a Content Server and use the remote server options to add books. This is not something I have tried to setup and use yet as my workflow does not rely on RDP-Calibre, I do all my metadata updates using a desktop client that I only run at the time I wish to do metadata updates.

The issue you had has been fixed and it wasn't an issue that would have impacted normal usage as the manual link you were having issues with was to manually edit a book entry. Regardless the issue was fixed and the docker updated within the weekly update schedule that I follow

The lazylibrarian-calibre docker has been updated Please note that the Calibredb import program should always be set to: /opt/calibre/calibredb in the config as noted in the settings image at the start of this thread.

The download dir should be "/downloads" and that should then in turn be mapped to the path where your downloader places completed book downloads. For me that would be "/mnt/cache/appdata/downloads/".

Calibre in a seperate docker can't be used by LL to do the post processing. You can use RDP-Calibre to manage the library manually if you want LL to post process with Calibre you need to use a docker with calibre and LL both in it

You will need to "Library Scan" for it to scan the book folder / calibre db

I mostly use the linuxserver.io dockers, and both of these are use the linuxserver.io base images.. And I liked the color scheme for the look Honestly if there's a problem with it I'd have no problem changing it.

For the calibre integration to work properly you need to use calibre (or calibredb) to import the books into your library. If you use calibre (external to LL) then you will need to do a library scan to search for the books that were added. If you use LL with calibredb as the post processor LL should update for that book on it's own without needing to rescan the entier library.

DOCKERS LazyLibrarian-Calibre: Adds Calibre to the linuxserver/lazylibrarian base image to allow LazyLibrarian and Calibre to share the same library location. Docker Hub: https://hub.docker.com/r/thraxis/lazylibrarian-calibre/ Github: https://github.com/Thraxis/docker-lazylibrarian-calibre After install configure post processing as below: Transmission-nzbToMedia: Adds nzbToMedia and Transmission with a modification to the linuxserver.io transmission docker to use alpine.python as the base image instead of alpine. Docker Hub: https://hub.docker.com/r/thraxis/transmission-nzbtomedia/ Github: https://github.com/Thraxis/docker-transmission-nzbtomedia

Could you post the log files, there are two of them one in the appdata folder and one when you right click the docker. Mind takeing a screenshot of your docker settings. //mace I had to go into the userprop.db and add in the prop_superuser value by hand. I've got it up and going now.

I've just spent a very unfruitful 2+ hours attempting to get the OpenVPN-AS docker to work. In a nutshell it didn't. I tended to get one of two outcomes. The admin account just didn't exist and you could not log in at all using openvpn as the password. The admin account was created but when you logged in you get. "You do not have Administrative permission" For the second case a check of the logfile will show that "Admin UI access is denied to user admin (not a superuser)"

The attachments seems to have gone missing after the forum upgrade.