#Gitlab still doesn't support issue templates in #yaml, the way #Github and #Forgejo can. Only #Markdown, which is a lot less attractive. But #Github and #Gitlab can do label changes in the Kanban (project) view, which #Forgejo can't.
you know hacking kubernetes manifests is so much more comfortable in python... is there any drive to get a yaml processor into the python standard lib?
I had several freezes of my old laptop that runs Proxmox due to a stuck CPU fan. I googled a bit and found an elegant solution for temperature reporting: a command_line sensor.
Nevertheless, it took several hours to configure it correctly (I forgot how to deal with ssh keys and similar).
I installed the ‘Terminal & SSH’ add-on in to home assistant.
I created SSH keys, put them into /config/.ssh folder, and copied to my proxmox server. Read these instructions. I’ve put something like this in my HA Terminal addon:
$ mkdir /config/.ssh$ ssh-keygen <em># generated ssh keys and when asked, i enter the folder /root/config/.ssh</em> $ ssh-copy-id -i /root/config/.ssh/id_proxmox root@MY_PROXMOX_IP <em># copy keys to my prox server</em>$ ssh root@MY_PROXMOX_IP <em>#try out if I can log on without password prompt, then exit</em>
I had to find out where my proxmox stores temperatures. I ssh’ed to my proxmox again, browsed folders and looked into files which one store temps. My AMD laptop stores it in /sys/class/thermal/thermal_zone0/temp.
It could be also …/thermal_zone1, 2, 3 or similar.
Then I pulled temperature data via SSH to HA terminal:
When I publish a blog post, the WordPress Activitypub plugin delivers the post to the #fediverse. This causes the CPU to heat to 75C+. I know it now, because I can track its temp. in HA.
🧵 The problem with my syntax seemed to be how I'd lovingly formatted some multi-line #YAML, yet it didn't get translated back into valid shell syntax. I abandoned that approach in favor of a super-log and ugly one-liner.
There was a time when I used to code graphics drivers. I used to love #assemblylanguage. Nowadays, I can't code my way out of a paper bag. Its been so many years and I'm just a #yaml jockey these days. I've been trying to learn #python, and while I get the basics, it just doesn't seem to gel in my head to make an app. I want to like Go, but I feel I gotta get something down like python to get to that (and to do some projects I want to do). The goal is to learn #vala, but man, I'm dying here!
I know that #json was never initially designed for configuration, but is there anything out there that actually works better for nested configuration settings? #yaml seems unsafe and easy to break, and #toml is simple but doesn't handle the nesting well. Perhaps nested configs are just a bad idea and we should stick with #toml?
Just spent 30mn on an unknown python script.
Haven't touched python in a long while.
30 mn to experiment/discover that os.environ.get('var_name') for a bool takes 'True', 'true', but still will consider the var as string. And a if my_var that is a string with 'true' in it will pass as bool true.
I don't understand how people can be angry about yaml, and are ok with python.
What? A network utilities management tool (for YAML config files) developed for 7 years.
◉Way back mainly for enterprise cases where network configurations required to be copied across hundreds of workstations in a whiff
◉Ifconfig can be used as always via nettools - this is extra for specific needs - not a replacement for network-manager
◉Simultaneous WPA2 & WPA3 support
(NOTE: This post is neither a complaint nor an invitation to complain about an individual's decision to stop providing volunteer labor in the form of maintaining his package.)
Since #Rust Crates.io started giving #RUSTSEC warnings on the unmaintained status of #yaml-rust library, there's a bit of a panic, not in the least because 1,000's of crates depend on it.
This article by the maintainer of Insta snapshot testing tool gives a nice analogy to Collateralized Debt Obligations (CDO's) with considerations on whether you should fork or might vendor the lib.
Aber: ich soll keinen YAML Parser wie #yq verwenden, weil das wird dann zu #kompliziert.
Ich soll also was tun?
Selber einen YAML Parser mit viel grep, sed, awk etc. bauen? Dafür 100 Stunden brauchen und danach etwas haben was noch viel komplizierter ist und beim ersten Sonderzeichen anfängt zu brennen?
OH: “None of these galactic fuckheads seem to realize YAML’s a goddamn data exchange format, not the fuckin’ language of the spheres, forged by the seraphim at the dawn of time, held securely in its place of honor in this one directory that’s checked into git”
This weekend, on Sunday afternoon non-important facts - the meaning of the YAML language abbreviation👇🏼
I always thought the YAML language abbreviation was Yet Another Markup Language, which is partially true.
The YAML language was created by Clark Evans, Ingy döt Net, and Oren Ben-Kiki in 2001. It was first named Yet Another Markup Language, as at that time, there were many other markup languages such as XML, SGML, etc. Later, in April 2002, it was renamed to YAML Ain't Markup Language.
I'm curious to know how others version control their private configuration files / docs / wiki. For now, I've created a #Gitea#Docker stack on my home network. Instead of copying the files I want to track into another folder and pushing from there, I've created hard links. Any other suggestions? #git#config#versioncontrol#linux@gitea
@5am I use @gitea (self hosted) and keep all my #k8s (k3s, actually) and whatnot in different projects. I use #1password’s op command to inject secrets into the various #yaml files. I use just to automate common tasks. It all works great.
On Feb 1st, 2024, #Apple released Pkl. Pronounced "pickle", it is a complete configuration scripting language, including a JSON/YAML/XML/more compiler, a language server, bunch of IDE plugins, and of course direct bindings for your favorite programming language, for quick adoption. A #Python binding seems missing.
I like how a Pkl config's specs and values are colocated. Always hated maintaining separate schemas for very simple configs.
@frankel just because people missed the "declarative idea" of k8s manifests.
#YAML is simple if you just do yaml with it, no anchors, no templates... Just declarations!
And I see the inappropriate will to "DRY", but you must accept some duplications is the way, it's better than dirty and complicated string manipulations