Its a fork of Calibre-Web not Calibre

Yeah that mostly ironed out by 11.11.

But its also a different philosophy where JF caches more in RAM than it did before, but that’s available for use by other proceases if needed.

I can’t think of a feature that KOReader provides that isn’t already in the Kobo software.

There are many many such features, such as

• style tweaks where a book’s CSS can be altered,
• plugins
• an in-depth progress and session tracker,
• the ability to ghost pages (like copyright and index) so they are skipped and don’t contribute to progress stats.
• RSS reader
• Progress syncing between instances

The killer feature for me however was in-page footnotes, so they show up at the bottom of the relevant page rather than having to trigger a popup or follow a link.

It also supports wireless transfer from Calibre-web, direct download via OPDS from a Calibre server or online providers like gutenberg, or syncthing.

The problem is, as you’ve experienced, there are so many tweaks and features that it takes a long time to get to grips with the possibilities.

BR is 25/50G, 4K BR is 66/100G

Muxarr, though Auto forced subs is a matter for your media player language settings not the files themselves.

sometimes there’s trouble restarting after power failure, depending on what order the database, pi, and various containers come back up.

depends_on solves this problem

Compose is just a way to have docker run services (apps) based on a list of settings in a text file rather than from commands in a terminal. It makes it easier to manage a whole stack (collection of services), and sets out the settings in a more human-readable format, so once you get how one service is configured, it’s easier to try others.

I found the guides overwhelming too at the start, but then I skipped them and just went for it with a simple container in a compose file (doesn’t even have to be sonarr).

The benefit of containerisation is that if you break it, it’s simple to remove the container, delete the config folder and start again without affecting your system. Give it fake data files to munch on and it’s unlikely to ruin anything if you muck it up.

So I did that a few times until I got the basic relationship between the docker compose file and the functions of the program. THEN I looked up some guides on the arrs and saw I needed to structure the volumes better, but that’s fine because I could wipe clean and go again.

Only when it worked predictably and I understood it did I let it loose on my library.

The good news is that if you figure Sonarr out, Radarr is almost exactly the same. As are all the arrs.

And then if you need some of them to route through a VPN container, that’s just one line in the file. And so on. Before you know it there are 20+ services and they’re easily managed.

So from services on a single compose, I can mark a show to follow, it’ll automatically download on release, rename itself, any extraneous subtitles and audio tracks removed, ingest to the media server, and delete the files when they’ve been watched. Basically, all I do is ask for the show and watch it. Everything else is automatic.

Just let Sonarr/Radarr do the renaming automatically.

Sonarr accommodates season un/monitoring and show-level quality profiles covering source, resolution and/or bitrate.

That risks breaking the drive eventually. They don’t handle loss of power well. And if its being written to at the time, data loss and corruption is inevitable.

That said, no need to reboot to mount the drive.

sudo mount -a

Having Prowlarr behind a VPN is not recommended, as some trackers ban VPN use. Instead have Prowlarr on the host network, and route individual trackers via Gluetun’s http proxy.

I don’t have books, moved music to navidrome, and have a relatively small library and it just will not play nice. Library scans lasting for days kind of nasty. RAM and CPU domination.

If only 10.11 were usable for me at all.

Zagreus is a maintained fork of Lunasea

We provide a web service on the example domain hosts to provide basic information on the purpose of the domain. These web services are provided as best effort, but are not designed to support production applications. While incidental traffic for incorrectly configured applications is expected, please do not design applications that require the example domains to have operating HTTP service.

Fix the shitty server first though.

For me it was far too hungry on CPU at “idle”.

Not Lazlow’s fault. You see, back then periodicals actually had sub-editors.

Find your nearest Kennedy