CWA nextgen is an active maintenance/bug-fix fork, link: https://github.com/new-usemame/Calibre-Web-NextGen/tree/main

Hi, I'm a HA and HK user personally, and it doesn't at all have to be an 'either-or' scenario.

First, and foremost, RatGDO works exceptionally well with HK with the native homekit firmware: https://github.com/ratgdo/homekit-ratgdo. It's rock solid and responsive, and I've been using the original RatGDO device since the whole API fiasco years ago.

Second, HA (or alternatively Homebridge), can both be used to connect non-homekit devices into the homekit ecosystem. That was my primary use-case of HA. For example, our hodge-podge collection of Govee light strips, Doorbell, Tuya switches, and Lifx bulbs are all in our Home apps. The kids + spouse don't know any different, it's all just in Home and responds to 'hey siri', including the garage.. There's various plugins for many devices, and with the homekit addon, you just pipe all your devices right into HK.

Then, with HA, you get the added bonus of your own Dashboard. For example, I use this to see what's playing on the various screens around the house. You can also do more complex automations, which can include services you don't hook into HK like your kids minecraft server, etc.

The point being, you don't have to choose one or the other, HA was incredibly useful for me to get stuff INTO homekit, and for the family that might be all they interact with. While you on the backend get more control tothen tinker with the automations, 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.

It does have a ‘Primarily AC use” setting in power management, thanks so much for the lead there!

Another option is to use Image File Utilities on the Pi to create an image backup. You can use cron + a bash script to create incremental backups using the tool (e.g., take a 'fresh' backup each month, with daily incremental backups in between). I mount a network 'backup' drive (a local NAS, but you could use anything) to save the image to so I can actually access it. Then, just use balena etcher to flash the backup iso in the event of a failure.

• Here's Image File Utilities: https://forums.raspberrypi.com/viewtopic.php?t=332000
• And a backup script + cron entry: https://forums.raspberrypi.com/viewtopic.php?p=2199452&hilit=cron#p2199452

Took a look and looks great!

How do I view (and block) instances?

In Voyager I can long press on them from the post. I don’t see the instances in the Arctic posts and my instance blocks aren’t showing up in filters/account blocks for my account.

Check out Tranga as a direct replacement to Kaizoku. Works nicely with Komga and/or Kavita as a reader. Add Komf to the mix for metadata management, nice covers, etc.

On iOS Paperback works as a free reader that can sync with Komga/Kavita

As OP mentioned this setup kind if like Plex but for Manga

Ha yes, once! I just used Balena Etcher and it worked exactly as expected.

Happy to help! There’s plenty of other options too (e.g., SSD) as folks mentioned, but this works well out of the box with no additional hardware. SD has been absolutely fine for my use (Pi-Hole), while still requiring maximum uptime so the family doesn’t riot if the internet is out.

Would you be willing to share your configs for niri and waybar? I'm new to Linux and trying to learn how to set stuff up like this. Looks amazing thanks for sharing

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.

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').

Would you share your dot files for this one too? Thanks!

Thanks for this, I have a similar setup and looking to migrate from Kavita -> Komga + iPad reader. For Paperback, does syncing read progress actually work to/from Komga? In the Komga instructions for syncing it directs me to install a custom Paperback tracker that only works for v.0.7 (and Paperback is currently v.0.8).