modifications for existing calibre library/config

[geolaw]

Not really an issue, but maybe a suggestion.

I've been containerizing many of my local services and calibre is my latest adventure. I've been running calibre-server on 2 machines locally for several years - I have a couple libraries that I maintain. I've written a script that let me add books, delete books, etc via the calibre api - which out of the box this base container did not support.

So I've tweaked some things in my deployment of this docker container (running with podman on Fedora 35).
I added a volume that gets mounted on /config and then moved the start script from the root directory into /config and then sym linked it back to root. I then can tweak the start script to enable the "--enable-auth" option to allow uploads via the API.

I also symlinked /root/.config/calibre to /config/calibre which then let me re-use my existing calibre config with my username, etc

I know I could probably fork this but just figured I would comment here.

[wietsedv]

Thanks for the suggestion. I'm not 100% sure anymore about the circumstances when I made this image - and I do not use it anymore - but I wanted to use the API without any authentication within a protected Docker network. Additionally using user/pass seemed like an unnecessary inconvenience to me. I think uploads would work with IP whitelisting, but I'm not 100% sure, and I'm unfamiliar with Podman networking.

In any case, linuxserver/calibre might work better for you. It's trustworthy, auto-updates and has easy auth configuration.