die-welt.net

I finally upgraded my mail server to Debian 13 and, as expected, the Dovecot part was quite a ride. The configuration syntax changed between Dovecot 2.3 (Debian 12) and Dovecot 2.4 (Debian 13), so I started first with diffing my configuration against a va

Somehow this whole DevOps thing is all about generating the wildest things from some (usually equally wild) template. And today we're gonna generate YAML from ERB , what could possibly go wrong?! Well, actually, quite a lot ...

We recently bought some Govee Glide Hexa Light Panels , because they have a local LAN API that is well integrated into Home Assistant . Or so we thought. Our network is not that complicated, but there is a dedicated VLAN for IOT devices. Home Assistant ru

If you're still using Vagrant (I am) and try to boot a box that uses UEFI (like boxen/debian-13 ), a simple vagrant init boxen/debian-13 and vagrant up will entertain you with a nice traceback: % vagrant up Bringing machine 'default' up with 'libvirt' pro

JP was puzzled that using podman run --memory=2G … would not result in the 2G limit being visible inside the container . While we were able to identify this as a visualization problem - tools like free(1) only look at /proc/meminfo and that is not virtual

Everybody is trying out AI assistants these days, so I figured I'd jump on that train and see how fast it derails. I went with CodeRabbit because I've seen it on YouTube - ads work, I guess. I am trying to answer the following questions: Did the AI find t

Back in 2020 I posted about my desk setup at home . Recently someone in our #remotees channel at work asked about WFH setups and given quite a few things changed in mine, I thought it's time to post an update. But first, a picture! img alt="standing desk

Everybody (who runs containers) knows this situation: you've been running happycontainer:stable for a while and it's been great but now something external changed and you need to adjust the code while there is still no release with the patch. I've encount

The Grandstream HT802V2 uses busybox' udhcpc for DHCP. When a DHCP event occurs, udhcpc calls a script ( /usr/share/udhcpc/default.script by default) to further process the received data. On the HT802V2 this is used to (among others) parse the data in DHC

I had reported this to Ansible a year ago (2023-02-23), but it seems this is considered expected behavior, so I am posting it here now.TL;DRDon