Yep! for a while I deployed Calibre-Web alongside Calibre in a ‘books’ compose.yaml stack using Docker. I used volume mounts to expose my library to both containers. The main thing to be cautious of is that you don’t write to the db from both C and CW at the same time (which could result in corruption). Some folks spin up/down Calibre as-needed, but I had them both running and was just mindful. I personally ended up switching from C+CW to Calibre-Web Automated and fully removing Calibre. I’m able to do everything from CWA that I was doing in both previously. FWIW if you are managing devices (e.g., family, etc.), Kobo devices + Kobo sync via CW/CWA is wonderful for usability (books show up on devices ‘natively’).

I use shelfmark (link: https://github.com/calibrain/shelfmark) with my hardcover API for metadata, connects seamlessly with calibre-web-automated (link: https://github.com/crocodilestick/Calibre-Web-Automated) for imports, etc.

I switched from Termius to Termix: https://github.com/Termix-SSH/Termix. Same idea, I wanted open-source, free (they state ‘forever-free’), and self-hostable. I used the Proxmox helper-script to install the ‘server’ as an LXC on my homelab, and then there are ‘clients’ for Linux, Windows, Mac, iOS, Android, etc. I just copied my SSH credentials, hosts, and snippets over from Termius and haven’t found a need to go back. I’m a relatively novice user and found xpipe a bit complex for my use, but it’s another solid option too.