In that case it’s definetly worth it to try this out, just so you have one more notification to disable
In that case it’s definetly worth it to try this out, just so you have one more notification to disable
I’m running Aurora DX on work and personal laptops. Also a gaming / media center box, which uses a custom ublue-silverblue based image that has ZFS modules installed (the box is also used for local homelab backups)
As long as you can get to the flatpak/container mindset, the atomic distros are absolutely brilliant.
Thanks for the info, but Matrix first…? I had to install the app again and try it out, but couldn’t figure out how to start a new matrix chat.
I really like the client UX/UI-wise, but unless I’m missing something it’s definetly not a viable Matrix client yet.
Yeah, you can use Element web and reset the account password using “forgot password” to use the beeper homeserver, but OP is asking about Android clients
The Beeper client is 100% not usable for Matrix-to-Matrix messaging, I don’t think it even supports e2ee, but I have heard they’re working on it.
Does the new Beeper Android client already work with Matrix messages? I tested it briefly after the release, but it basically didn’t support regular Matrix at all yet
I didn’t read all the comments, so someone may have pointed this out already.
One of the main ideas is probably something like Fedora CoreOS, where the Quadlet systemd files are automatically created during first boot with something like Kickstart or cloud-init.
Instead of shipping the applications with the image, the OS image can be very minimal, while still being able to run very complex stuff.
When you add the fact that CoreOS and other atomic distros can update themselves in the background, and boot to an updated base image, the box just needs periodic reboots and everything stays updated and running with basically no interaction from the admin at all, best case.
Probably not so useful in the self-hosting / homelab context, but I can imagine the appeal on a larger scale.
I’ve been using Quadlet+Podman kube YAMLs for a while for my own self-hosted services, and it’s pretty rock solid. Currently experimenting with k3s, but I think I’ll soon switch back. Kubernetes is nice, but it’s a lot more fragile for just a single node. And there’s way too much I don’t understand…
I wrote a couple blog posts about the homelab setup, planning to add more when I have time. Give a read if you’re interested: https://oranki.net/tags/self-hosting-my-way/