Calibre-Web Automated (CWA) is a reasonable modern alternative to a legacy Calibre-Web container, but the forum thread does not show that IceWhale actually replaced the App Store package. IceWhale only replied that the team would check the request.
For users who want CWA now, the upstream project recommends Docker Compose and provides an explicit migration path from stock Calibre-Web.
Why the User Wanted to Replace the Legacy App
The February 2026 post argued that the existing Calibre-Web package was no longer keeping up with newer Calibre desktop database changes. That was the user’s assessment; IceWhale did not confirm the exact breakage in the thread.
CWA Is Actively Maintained Upstream
The current Calibre-Web Automated repository documents an actively developed project with a recommended Compose deployment.
The current stack uses persistent /config, /cwa-book-ingest and /calibre-library mounts and exposes the Web UI on container port 8083 by default.
Migrate From Stock Calibre-Web Carefully
The upstream CWA guide says existing Calibre-Web users should stop the old instance, reuse or copy the old /config, and map the existing library to CWA’s /calibre-library. Make a copy first so the old container remains recoverable.
The ingest directory is not the library: CWA processes and removes files placed in /cwa-book-ingest. Do not point that path at your only copy of the book library.
Install It as a Customized App on ZimaOS
Use the upstream Compose file as the starting point, replace example host paths with persistent ZimaOS storage, set PUID/PGID and timezone, then import the reviewed Compose into ZimaOS.
The custom Docker app guide covers the ZimaOS side of that deployment model.
Do Not Delete the Old Calibre-Web Until You Verify CWA
Start CWA on a temporary different host port, log in, confirm users/settings, browse the library, ingest a disposable test book and restart the container. Only then retire the legacy instance.
Bottom Line
The forum request was acknowledged but not confirmed as an App Store replacement. CWA can still be deployed directly through Docker Compose, and its upstream migration path makes that safer than waiting for a package swap. Preserve the old config/library first and test the new instance before removing the legacy app.
