I've spent the last 3 months building `ebookfs`, which is the ebook library software I've always wanted after being intrigued by Plan 9/9P and not gelling with Calibre.
The current release is v1.0.0-beta-3, since I know there's a few bugs & I haven't put it through enough testing, so I'm sure there's more to find.
Right now it's only built to be accessed via a 9P mount and run on a server (like the k3s cluster I've got in my homelab). However, I got to a point where I realised I'm solving and re-solving a lot of the same problems that Calibre and other attempts at replacement software has to, for the sake of a different interface. So, I made the decision to keep the 9P code separated from the core library code and build the library core as a generic interface with the idea that other frontends should be able to be built, whether that's HTTP + web or a TUI etc. Essentially, that library module is what I wish I could have had before working on this project.
There is also a roadmap for V2 I've put together to add hooks to the ingestion process, so plugins could be built to convert to EPUB or strip encryption, as well as emitting events when books are edited or deleted. The latter would push some of the logic I've written in the 9P layer back into the library.
Hopefully some of y'all like the idea of the filesystem interface, which is kind of an open core that scripts and other things could be built on top of, and hopefully some of y'all like the idea of throwing your own frontends together.
I've spent the last 3 months building `ebookfs`, which is the ebook library software I've always wanted after being intrigued by Plan 9/9P and not gelling with Calibre. The current release is v1.0.0-beta-3, since I know there's a few bugs & I haven't put it through enough testing, so I'm sure there's more to find.
Right now it's only built to be accessed via a 9P mount and run on a server (like the k3s cluster I've got in my homelab). However, I got to a point where I realised I'm solving and re-solving a lot of the same problems that Calibre and other attempts at replacement software has to, for the sake of a different interface. So, I made the decision to keep the 9P code separated from the core library code and build the library core as a generic interface with the idea that other frontends should be able to be built, whether that's HTTP + web or a TUI etc. Essentially, that library module is what I wish I could have had before working on this project.
There is also a roadmap for V2 I've put together to add hooks to the ingestion process, so plugins could be built to convert to EPUB or strip encryption, as well as emitting events when books are edited or deleted. The latter would push some of the logic I've written in the 9P layer back into the library.
Hopefully some of y'all like the idea of the filesystem interface, which is kind of an open core that scripts and other things could be built on top of, and hopefully some of y'all like the idea of throwing your own frontends together.