Adam Kaminski thimslugga

Linux Networking Reading List

Currently in no particular order. Most of these are kind of ancient.

Where's all the modern documentation? So much of what I've turned up searching is other folks complaining about having few options beyond reading source code.

The OREILLY books, while dated, seem to be some of the best available. Note that these can be read with a 7-day trial. Do this! At least get through the introduction section and first chapter of each to see if it's what you're after.

https://www.netfilter.org/

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

I use git worktrees a lot, and I’ve been annoyed by the repo itself having effectively a privileged worktree that’s always there (and refuses to let any other worktree check out the branch it’s on). And then not having a good place to put my other worktrees. If I clone to $PROJECTS/this-project, where do I put my worktrees?

If I put them in the directory, the worktree directories are scattered among all the files in the clone’s working tree (and I seem to remember git having some issues with worktrees inside a working tree), but
if I put them next to the directory, then the worktree names need to be prefixed with the repo name (and if there are repos foo and foo-charts, it’s easy to forget that foo-charts isn’t just a worktree of foo.

So, my projects tended to look like this:

$PROJECT_DIR
├── my-project                           # a repo
│   ├── .git
│   └── ...                              # but also a working tree

Claude Code VM Setup

Idempotent bootstrap script for an Ubuntu 24.04 LTS development VM
optimised for Claude Code agent sessions.

Run it once to install everything. Run it again to update. Safe, transparent, and documented at every step.

Why this script?

Home Automation Infrastructure – Full Technical Documentation

Proxmox VE 8 • Home Assistant OS • Docker Stack • Raspberry Pi 5 Services

This document describes the complete home automation environment, including all installation steps, configuration details, and troubleshooting actions required to get the system fully operational. It is formatted for GitHub Gist.

1. Network Overview

| Device / Service | IP Address | Description |

Proxmox VE – Complete Backup & Restore Plan (NVMe Failure Scenario)

This document is the single authoritative backup and restore guide for a standalone Proxmox VE host. It is written to be usable during a real failure (NVMe disk read/write issues) but with the premise that the Proxmox VE host is still running and accessible (to try to create VM backups).

1. Scope and assumptions

Single Proxmox VE host (no cluster)
Proxmox VE 8.x backups, restore onto Proxmox VE 9.1-1

description: Manage Proxmox Virtual Environment infrastructure. Monitor nodes, manage VMs and containers, and perform SRE operations. homepage: "https://www.proxmox.com" metadata: moltbot: api_base: PROXMOX_HOST/api2/json category: infrastructure emoji: 🖥️ name: proxmox

The Goal

To create a Debian VM that is ready for Ansible using Terraform/OpenTofu, Proxmox VE, and Cloud-init.

Requirements

You will need to:

have a running Proxmox server whose console you can reach, via either web GUI or SSH
have Snippets enabled on at least one storage location with your customized ci-user.yml and ci-net.yml file in it

	mkdir test-laya
	cd test-laya
	uv init
	uv add 'laya-coreml[demo]'
	hf download aac6fef/laya-multilingual-coreml-ane --local-dir models/snake
	uv run laya-coreml-snake --model models/snake

	#!/usr/bin/env python3

	import requests

	try:
	import json
	except ImportError:
	import simplejson as json
	import os
	import sys