docker-calibre-web VS audiobookshelf

Special mentions: Watchtower, Portainer CE, PhotoPrism, Dokuwiki, Calibre-web.

Calibra-web

So I surveyed docker images in my personal use:

Postgres (Docker provided - https://hub.docker.com/_/postgres): Debian (with alternates for alpine or other debian versions)

Jellyfin (Developer provided - https://github.com/jellyfin/jellyfin/blob/master/Dockerfile): They use an alpine build step but the final distributed image is debian

Calibre-Web (Linuxserver provided - https://github.com/linuxserver/docker-calibre-web/blob/maste...): Ubuntu

Graylog (Developer provided - https://github.com/Graylog2/graylog-docker/blob/4.2/docker/o...): Debian

Vaultwarden (Developer provided - https://github.com/dani-garcia/vaultwarden/blob/main/docker/...): Debian (with alpine alternate available)

For professional use, our company mandates all images used are built off a common base image, which is Ubuntu based (my previous employer was similar, but used a Red Hat based image).

On the (e)book side, I'm running calibre (which runs the desktop app accessible by guacamole, for management, only accessible on my local network) in combination with an instance of calibre-web, in order to access the files remotely.

Jellyfins book support is kinda eh right now, it'll probably take another major version or two. I'm using calibre-web until JF feels ready. Clients shouldn't be a problem though, any web browser will do.

Also, here's an issue that has been opened: https://github.com/linuxserver/docker-calibre-web/issues/119

For anyone who's game to run another service for audiobooks, I've found Audiobookshelf to be pretty good: https://github.com/advplyr/audiobookshelf

A spotlight on AudioBookshelf, an audiobook and podcast streaming server

The basics are same across most any container, you probably need to map some network ports, and map some storage paths, and then you are pretty good to go. There can be more than that, but those are kind of the minimums. For instance, the example compose file for audiobookshelf does just that, maps a port, and some storage and that's about it.

linky: https://github.com/advplyr/audiobookshelf#readme (JS; GPLv3) and they have their own app, too: https://github.com/advplyr/audiobookshelf-app#readme (Capacitor GPLv3)

Move away as in find another audiobook vendor? Or simply retain access to your existing collection?

Audiobooks from Audible can be downloaded via the UI. They will have DRM, but it's possible to remove.

If you have audiobook files without DRM you can listen to them via any app that plays audio, but there's also at least one OSS project that aims to fill audiobook UI niche [1].

[1]: https://github.com/advplyr/audiobookshelf

Using Audiobookshelf (https://github.com/advplyr/audiobookshelf) and hosing my own podcast with an rss feed. It works just perfect in other podcast apps but in Pocket Casts, that used to work, I can't no longer see new episodes starting from about a week ago. I have never been able to stream the episodes either, just download and listen, this also works in iOS Podcaster app.