this post was submitted on 09 Apr 2026
443 points (98.3% liked)
Technology
83631 readers
3989 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Agree, though calibre-web exists and runs in a single Docker container. I've been using it for a few years, and it's great.
Sure its a whole Linux server under the hood just to run Calibre and the services required to give it a web interface and API for reading apps - making it way bigger than it needs to be - but it does the job.
Calibre-web isn’t Calibre. It uses the same database, but that’s about it, unless you use the optional conversion mod on the linuxserver container.
A docker container is preferred, but again, CW isn't Calibre. Same database but completely different management system + also lacking a lot of the sync opportunities.
The issue is that there's no open protocol for library syncing. It doesn't exist because all big players (Amazon, Kobo/Rakuten, B&N, etc.) have their own proprietary system, and need no open alternatives.
OPDS is a thing but it's meant to replicate a physical library (one you can walk into) in behaviour and approach, not a personal library (list all books I have and give me easy access to them). It's essentially just an RSS-style feed that has no defined structure, thus isn't software navigable - e.g. there's no guarantee you can list all book series, or all authors, and most implementations usually give you very roughly defined "recently added", or "hot now" book lists...
I've actually been working on a solution for this, something that provides an almost Kindle library experience (see all your books from a remote server, sync down the remote ebook file, sync back read progress, filter/search based on book properties, etc.), while being flexible enough for non-readers applications as well. But I haven't even gotten to the point where I can define the API contract properly, let alone the backing database and mapping to Calibre. Honestly at this stage I feel like the best approach is starting from scratch, establishing modern requirements, and going from there.
A docker container is not a whole separate Linux server, it uses the kernel running on the host
Have you seen the apt sources list that CW generates on boot? It's semantics. 😊
With default runtime, very true. There are other runtimes that can be used that provide better isolation like gVisor, kata, firecracker, etc.