fbrary VS audiobookshelf

example screenshot

Overview

I finished a side project of mine. It's a terminal based audio book catalog/library. It's not for listening to stuff but to organize it (completion status, rating, ...) and to search for stuff. As an avid audio book listener I have > 100 books and whenever someone asks me for a recommendation I cannot remember anything. You can find it here: https://github.com/b0wter/fbrary

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.