jgkawell

If you click the switch plan link in the blog post it'll let you change. That's what I had to do.

I've been using Neo Launcher for a while as a Nova replacement and it's pretty good. Both of those features are included as well as things like shortcut actions when you double tap or swipe on the home screen.

That's definitely its focus, but if you want a very simple store it does support payments: https://ghost.org/help/ecommerce/

If you're willing to accept JavaScript I'd recommend a Ghost setup. Pretty good platform once it's set up and easy to selfhost. Not sure you'll find a platform without JS for your use case tbh.

I have two of the U6 lite APs and they cover my whole house perfectly. They're POE but I just got a cheap POE unmanaged TP-Link switch for now.

I use yarr as well but forked it to use postgres as the database instead of sqlite: https://github.com/jgkawell/yarr

I'm experimenting with the Music Assistant add-on but it seems to be early days for that project. Could be awesome though as it combines media libraries from services (e.g. YouTube music) and self-hosted things (e.g. Navidrome) and plugs them into the Home Assistant ecosystem.

https://github.com/music-assistant/server

I'd recommend looking at the Wyoming/Piper/Rhasspy system. There's some really good minds working on it and it's got a big community behind it already. It's also plug and play with Home Assistant which is awesome. It's the system I use and while I'm still fine tuning it for my use cases it's already pretty great.

Haven't used it yet, but Proton has a beta desktop app that might be what you're looking for.

F-Droid apps typically lag behind GitHub releases because their build pipelines are different. So in this case the latest version (which supports the freshrss API) isn't available on F-Droid yet.

I don't know of anything built for that purpose but you could use home assistant dashboards to pull it off pretty easily if you already have an instance set up.

The solutions you've mentioned aren't exactly equivalent. Proxmox is a hypervisor while Docker Swarm and Kubernetes are container orchestration engines. For example, I use Proxmox in a highly available cluster running on three physical nodes. Then I have various VMs and LXC containers running on those nodes. Some of those VMs are Kubernetes nodes running many Docker containers.

I highly recommend Proxmox as it makes it trivial to spin up new containers and VMs when you want to test something out. You can create and destroy VMs in an instant without messing with any of your actual hardware. That's the power of a good hypervisor.

For orchestration, I would actually recommend you just stick with Docker Compose if you want something very simple to manage. Resiliency or high-availability usually brings with it a lot of overhead (both in system resources as well as maintenance costs) which may not be worth it to you. If you want something simple, Proxmox can run VMs in a highly-available mode so you could have three Proxmox nodes and set any VMs you deem essential to be highly-available within the cluster.

For my set up, I have certain services that are duplicated between multiple Proxmox nodes and then I use failover mechanisms like floating IP addresses to automatically switch things over when a node goes down. I also run most things in Kubernetes which is deployed in a highly-available manner across multiple Proxmox nodes so that I can lose a physical node and still keep (most) of my services running. This however is overkill for most things and I really only do it because I use my homelab to learn and practice different techniques.