
a Plasma 6 compatible widget for controlling Home Assistant entities from your KDE desktop.

Ive actually been personally moving away from kubernetes for this kind of deployment and I am a big fan of using ansible to deploy containers using podman systemd units, you have a series of systemd .container files like the one below
undefined
[Unit] Description=Loki [Container] Image=docker.io/grafana/loki:3.4.1 # Use volume and network defined below Volume=/mnt/loki-config:/mnt/config Volume=loki-tmp:/tmp/loki PublishPort=3100:3100 AutoUpdate=registry [Service] Restart=always TimeoutStartSec=900 [Install] # Start by default on boot WantedBy=multi-user.target default.target
You use ansible to write these into your /etc/containers/systemd/ folder. Example the file above gets written as /etc/containers/systemd/loki.container.
Your ansible script will then call systemctl daemon-reload
and then you can systemctl start loki
to finish the example
The Kde store UI is a bit lacking the screenshot browser has arrows all the way at the edges.
I uploaded three screens two of the configuration and one of the widget on a panel, expanded with all the advanced controls.
Edit: Ive reuploaded the images with the expanded widget first
A home assistant plasma panel widget
a Plasma 6 compatible widget for controlling Home Assistant entities from your KDE desktop.
I wanted something I could embed buttons in panels and configure from the GUI. Third plasmoid ive put together, second one I've published.
The fork Ansel, is supposed to improve on the UI situation.
Unironically their greatest movie.
That is some terminal biz brain right there.
Kate has excellent lsp support nowadays as well.
Pretty solid gameplay so far, threw a tenner at them for the work
I think the gap you have is in understanding that Podman Compose was meant to line up with the limitations of docker's compose, but technically is more capable.
Quadlet files let you do more complex workflows like deploying multiple copies of a service in your deployment that regular compose doesn't, while not running full kube.
The use I have is that I have something deployed in compose right now that I'd like to scale up on the box since i have the capacity for it, but dont want to deal with a full kube setup or the politic
Personally I've converted most of my single node k3s to using quadlet files instead as its less fragile. I absolutely deploy single containers in the quadlet. They show up in journalctl and the ergonomics are great.
Hi, i believe this is where https://groups.google.com/g/django-developers/c/C_Phs05kL1Q
They've explained why
Sometimes I flip that cheese over and let it crisp up after steaming it
Ah good to know, shame it's been left by the wayside a bit. Was super useful in the early days
Seems similar to the work done by https://sub.rehab