@bfdi Ich habe mittlerweile oft die Kelberultras Fanpakete, hier auf Mastodon, gesehen . Die sind schon sehr schickt. Wie kommt man dann an ein solches?
Mal in die #Foodiverse-Runde gefragt: was verwendet ihr denn so für Bratpfannen? Ich bin in den letzten Jahren von Teflon abgekommen und bevorzuge eher Keramik-Antihaft (meist von WMF). Ich hab auch gusseiserne Pfannen, die ich regelmäßig mit Leinöl einbrenne, aber für den tagtäglichen Gebrauch ist eine mit Antihaftbeschichtung einfach bequemer.
Aber ich lass mich gern auch von anderen Standpunkten überzeugen. Retröts und Kommentare gerne erbeten.
@kharkerlake Deswegen hab ich mir auch explizit nicht das original gekauft. Die Replikas haben die gleiche Technik und sind deutlich billiger.
Hab meine jetzt ca 10 Monate, selbst nachdem der Kater sie einmal runtergeworfen und sie jetzt ne Delle hat funktioniert sie einwandfrei. Selbst dort ist die Antihaftbeschichtung nicht abgegangen.
Giving up on configuring #forgejo to send e-mails. No matter what I try, it can't authenticate to my mail server. "Password mismatch" though it works without problems when I connect with my normal e-mail client, so I know the password is correct. I tried putting the password as PASSWORD and without the backticks in app.ini, no luck.
SOLVED: The key in app.ini is named PASSWD not PASSWORD. #facepalm
Opinion: people who staunchly prefer working with Gerrit, and consider anything else inferior, really love working with git-review. And if git-review were not Gerrit specific they would be just as happy with, say, GitLab.
The process that the git-review/Gerrit combo automates/enforces (one commit per change, automatically generated topic branches, change IDs with cross-project uniqueness) could also work just fine by hooking up git-review with the GitLab API.
@xahteiwi as someone who wants to contribute to OpenStack, the first time I had to work with Gerrit, I instantly hated it because I'm used to Pull Requests / Merge Requests and their workflow. Gerrit feels "wrong" for me.
@waldi sag mal kennst du jemand der sich mit APT etwas besser auskennt? Wir haben hier nen merkwürdiges Verhalten unter Debian 12 und kommen gerade nicht dahinter was da passiert.
Hey, ich habe eine Startup-Idee, und damit werde ich locker einige Milliarden einsammeln!
Onshore-Windturbinen sind ja schwer zu bauen, weil sich die Rotorblätter und Turmbauteile nicht leicht transportieren lassen auf der Straße.
Mein Shoplifter-Startup wird daher einige tausend elektrische Quadcopter-Drohnen kombinieren und mit ihnen das Rotorblatt zur Baustelle und dann zur Montage direkt auf den Turm hieven.
I'm running small MySQL 8 instances in Kubernetes, and
they don't use any replication at all, ever, and
they have an RPO of several hours in the past (meaning: if they break, they can just be redeployed and re-populated from a backup that is a few hours old, and there is an automated procedure for that, which runs several times a day),
@xahteiwi If I'm not completely mistaken this points to the ability to save the binlog statrow and file information with the backup. When you repopulated with the backup mysql can redo all operations stored in the binlogs since the restore time and you get a DB that's up to date.
Not sure, if this would be applicable to your scenario
If you don't know this yet and you feel like nerding out, spend a bit of time this weekend on the question of where gold comes from — as in, how the element gold is made in the universe.
(Don't spoil it for others. Let their minds be boggled, too.)
Dear #lazyweb. When your task is to find a basic system to handle tickets (not many and only a handful of people handling them) and you want to make it a bit more future-proof so you can naturally add more features like knowledge sharing and tracking changes to content, if needed.
Do you think it's OK to (ab)use the issue system of Gitlab or Gitea/Forgejo instead of introducing a dedicated ticket system?
Just when I thought I'd seen it all, I see generated Dockerfiles that behave differently based on what version of Docker is installed on the build host.
Reproducible builds? Container images as immutable build artifacts? Anyone?
The container crowd has played us for absolute fools.
While playing around with group_vars in #Ansible, I noticed that a specific host never applied the variables defined in the group_vars.
To verify that a host is actually a member of the wanted group(s), I needed a quick way to check for group memberships. Here's a possibility how to do that. 👇