I hope this isn’t a step towards replacing the native app with an SPA.
From the Readme:
Why does it exist? 🔓
Calibre, while a fantastic tool for its age, has several problems when containerised, including its reliance on a KasmVNC server instance for the UI, which is near impossible to use on mobile and is relatively resource-heavy if you’re running a small, lower power server like I am.
For many, Calibre-Web has really swooped in to save the day, offering an alternative to a containerised Calibre instance that’s resource-light and with a much more modern UI to boot.
However, when compared to full-fat Calibre, it unfortunately lacks a few core features leading many to run both services in parallel, each serving to fill in where the other lacks, resulting in an often clunky, imperfect solution.
sxan@midwest.social 1 month ago
tofu@lemmy.nocturnal.garden 1 month ago
Which native app do you mean? Calibre desktop?
It’s by different devs. One is a desktop application, one a selfhosted Webservice. I think there’s room for both.
gedaliyah@lemmy.world 1 month ago
So is this a fork of calibre web or something that runs on top or what?
tofu@lemmy.nocturnal.garden 1 month ago
Idk if it’s a fork or rewrite, but it’s it’s own thing.
Kirk@startrek.website 1 month ago
This is explaining the difference between Calibre and Calibre-Web.
The person you replied to asked what the connection is between “Calibre-Web” and “Calibre-Web Automated”
tofu@lemmy.nocturnal.garden 1 month ago
It’s both
Kirk@startrek.website 5 weeks ago
Ah ok, so ignoring Calibre for a moment, what’s the difference between Calibre-Web and Calibre-Web Automated?
tofu@lemmy.nocturnal.garden 5 weeks ago
As I quoted, the dev found CW lacking features compared to C. That’s where CWA comes in. Check the Readme if you want a comprehensive list of all additional features.
stephen01king@lemmy.zip 1 month ago
I don’t see any mention of calibre-web-automated in that comment.