Repo on Alwaldend

DNS management in a monorepo

Sun, 13 Sep 2026 00:00:00 +0000

Buying a domain is one of the best purchases you can make because they are very cheap and owning one offers you more independence - you can have your email not tied to a specific provider, you can have a site, etc.

After I bought a domain, I needed a way to manage DNS of that domain. Since using the registrar’s UI to do that is not the best idea, I searched for an IaC tool that can do that for me - I settled on DNSControl.

Slop without a clear goal

Sat, 12 Sep 2026 00:00:00 +0000

A while back, I said to Jipity¹: “Jipity, how can I improve agent ergonomics in this monorepo?”, and Jipity gave me some useful suggestions, but one of them was not like the rest. It said that context in the repo was too splintered — agents had to read many things in different directories to understand how things are done. In my infinite wisdom, I said, “Jipity, write me a comprehensive plan implementing a unified agent system with the goal of improving ergonomics in this monorepo”. And it wrote me a plan, I did not really read it.

Bzlenv

Mon, 01 Jan 0001 00:00:00 +0000

Rules to create a bazel environment which functions similar to venv

Features

Adds bazel-built tools to ${PATH}
Exports .env

Usage

Create env and activate:

. "$(bazel run //tools/bzlenv)"

Activate existing env:

. .bzlenv/bin/activate

Deactivate env:

bzlenv_deactivate

Repo

Mon, 01 Jan 0001 00:00:00 +0000

Setup

Install packages:

sudo dnf install \
  clang clang-tools-extra java-latest-openjdk-devel rust cargo mesa-libGL-devel \
  go Xvfb python3 gmp-devel patch podman git git-lfs fuse fuse-libs pcsc-lite pcsc-lite-devel \
  openssl gnutls-utils opensc openssl-pkcs11 libdnet qemu-kvm qemu-img

Install bazelisk: https://bazel.build/install/bazelisk

Symlink bazel:

ln -s ~/.local/bin/bazelisk ~/.local/bin/bazel

Install git hooks:
```
bazel run //:write_git_hooks
```
Install android tools:
```
ANDROID_HOME="${HOME}/Android/Sdk" \
  bazel run --config=agent \
    --repo_env=ANDROID_HOME= \
    //tools/android:install
```
The empty repository environment is required for the first installation so Bazel does not try to load the SDK before sdkmanager installs it. Afterwards, export ANDROID_HOME and ANDROID_NDK_HOME, or set both with --repo_env in the ignored user.bazelrc. The repository dotfiles export the expected paths.
Setup dotfiles (optional):
```
bazel run //projects/dotfiles:install
```
Install nvm: https://github.com/nvm-sh/nvm
Install node:
```
nvm install node
```
Qt is downloaded by Bazel; no host installation is required.

bazel run //tools/vault -- login --method=userpass username="${USER}"

Setup .bzlenv

. "$(bazel run //tools/bzlenv)"

Compile commands

Build compile_commands.json: