My home lab machines are running a mix of GNU/Linux, FreeBSD, and macOS and over the years I have accumulated a decent amount of shell scripts and tools, which eventually got refined as my personal Configuration Management system for keeping these systems up-to-date and sync configs between them easily.

Go supports a number of directives which can influence the behaviour of the compiler.

I use Org Mode for note taking and tracking purposes.

Couple of days ago I got my brand new Synology DS224+ disk station, which was meant to replace my current (and old) Synology DS213j system.

One of the things I like doing in my spare time is messing around with Software-defined radio (SDR).

My homelab setup hasn’t changed much for the last few years.

In the Setting up a Kubernetes cluster with Vault and OIDC trust post we’ve seen how to configure identity federation between a Kubernetes cluster and Vault.

In this post we will see how to create and configure a development Kubernetes cluster with Vault running in it and setup OpenID Connect trust between Vault and Kubernetes workloads.

Not long ago I have switched from lsp-mode to eglot and tree-sitter.

In a previous post I’ve talked about makefile-graph - a tool which lets you visualize your Makefile targets so you can better understand how targets relate to others.