yes of course let me deal with the spam problem someone else made my problem answering every fucking call that tries to scam me instead of letting the caller leave a voicemail if they're legit.
This is generally done when you have customers with SSO, the first one will take the email and if the domain is ssod it forces them through a particular workflow. Otherwise you get the other normal username/password flow
Mahindra started out by cloning the Willys and they sell something relatively modern in the states called the Roxor
there's been something that's really been rubbed me the wrong way about jeff in the last few years. he was annoying before and had some insights but lately I've been using him as a sort of a jim crameresque tech-take-barometer.
What really soured me was after he started picking fights with some python people a few years back because someone dared post that a web framework? (couldn't dig up the link) was a greater contribution to the world than S/O? His response was pretty horrid to the point where various python leaders were telling to stop being a massive dick because he was trying to be a bully with this "do you know who I am" attitude because he personally had not heard of the framework so it wasn't acshually at all that relevant compared to S/O.
and now this combined with his stupid teehee I am giving away my wealth guise look how altruistic I am really is a bit eugh
TIOBE merely measures the number of questions asked about a particular language online, which is obviously not exactly realistic metric but people for some reason love to spout it
Seeing as the XLibre fellows upstream commits were reverted because they were absolute dogshit, I don't think that the fork has legs
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
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.
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.
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.
the rivers...