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

[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

During my expirementation with some of these self hosted llms, I was attempting some jailbreaks and other things and thought would this be any good at ERP?

Only if youve never been with another human being.

The fork Ansel, is supposed to improve on the UI situation.

Kate has excellent lsp support nowadays as well.

Its a full linux os, so you can do literally anything that can be done with existing tooling. For example, I have syncthing installed on mine so i just have to drop files into a folder on another computer of mine and they show up.

The software folks have put together a decent experience in the last few years and its rather nice out of the box.

Glad i did not go with these guys when i was e-reader shopping, the lack of gpl sources was enough for me.

Went with a pinenote because the timing was good, and while it has some corners I dont except the debian install to become a ccp mouthpiece 🙃

Pretty solid gameplay so far, threw a tenner at them for the work

Stack overflow now with the sponsored crypto blogspam Joining forces: How Web2 and Web3 developers can build together

I really love the byline here. "Kindest view of one another". Seething rage at the bullshittery these "web3" fuckheads keep producing certainly isn't kind for sure.

Your family wants to see you post on threads bullshit is laughable

This is nothing, The characterAi subreddit was in full meltdown earlier.

This reminds me of when I was planning out a tubular bells project. there is an amount of crankery around various notes and I came across a series of videos about the various Cs and their use in healing or chakra alignment.

When i went to buy some tuning forks I noted some more weird mysticism, but hey at least they produced a nice set of C notes.

Id unironically quit and start a competitor, because they're so bogged down in this ceremony bullshit.

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

Man this company has had some really interesting ideas and then the execution always falters.

I was still subscribed when the first eve-fps crossover they attempted. it seemed great and then for whatever reason a console exclusive with a subscription fee ontop. They didnt get the numbers they were planning for and the whole thing just died on the vine.

They've had some neat tech here and there and the whole experience is great for building out your psychopathy but i lost interest after the Greed Is Good phase of CCCP games started.

Sometimes I flip that cheese over and let it crisp up after steaming it

I signed up to this instance because I feel this in my bones.

I cut my teeth on PHP CGI in the late 00's before shifting to python CGI because my university had banned PHP on the webservers.

Frontend wasn't exactly a term back then. I'd picked up a bit of jquery into my server generated Django templates, I was playing with template fragments in 2011 and life was good.

I mostly avoided the SPA fad, but a (short) stint at Wayfair had me end up writing react and dear God the amount of indirection and tomfoolery involved with effectively writing the app a second time left a sour taste in my mouth.

These days I mostly write embedded daemons in rust for Linux devices. I wrote a munin replacement in rust because packaging perl for Yocto is a struggle. I needed to serve a website, so I found a jinja style library, setup my templates and fragments and dropped htmx into the frontend.

Life is good again.

I have friends/coworkers who argue with me that I should write SPAs but they don't get that I mostly want to avoid fighting frontend tooling and get shit done. A backend serving templates is miles more ergo than react and I don't have to deal with the NPM upgrade treadmill. I don't get daily dependabot alerts.

Don't get me started on golang, meteorjs, and lambdas