Dotfiles Fleet Handbook

Ansible-driven dotfiles and infrastructure for a personal fleet. Three distinct concerns live here:

  1. Workstation config — shells, packages, browser, SSH, Tailscale, kubeconfig, GNOME, and more
  2. Home servers — bihar and karnataka (Bluefin + k3s, linked by KubeStellar); the hives run on bihar with karnataka as standby. The Talos manifests are archived
  3. Hosted infrastructure — OCI spindle (Matrix, public front door, hive failover coordinator) and the AWS account; the AWS Talos cluster is terminated

Current state of every host: Fleet status.

This handbook is public. It covers architecture, decisions and runbooks. Never put secrets in it. Fleet addresses live in inventory or come from just inventory; service runbooks may document public endpoints.

Quick Start

# Apply to local machine (most common)
just apply

# Apply specific tags only
just apply-tags kube,shell

# Apply to a remote machine
just apply-remote himachal

# Dry-run to see what would change
just check

# Lint all YAML and Ansible
just lint

Machine Fleet

Ansible-managed hosts, from inventory.yml:

MachineGroupTypeRole
kanpurdesktopLaptopPortable workstation
himachaldesktopLaptopPortable workstation; legacy hive_ops timers retired
dillidesktopDesktopSecondary workstation
keraladesktopMobilepostmarketOS ARM device
mumbaidesktopVMDebian VM on the phone, machine_profile: cli-only
punjabserverVMAgent box, KubeVirt VM on karnataka
bihardesktopServerHome server: active hive host, KubeStellar hub
goaserverServerRaspberry Pi 5 ARM server
vmserverVMLocal dev VM
termuxtermux_hostsPhoneRaw Termux/Android layer
test-fleet-fedora, test-fleet-node2test_fleetVMKubeVirt test VMs (vm-test)
matrixvpsVPSRetired — see the cutover runbook
telenganavpsVPSRetired — see the cutover runbook

Outside this inventory:

  • karnataka — home k3s/KubeVirt server, configured from the native-units branch. See Karnataka.
  • Spindle — OCI Frankfurt VPS: Matrix, LiveKit, the Caddy front door for the hives, and the hive failover coordinator.
  • The AWS Talos cluster was terminated on 2026-10-25, and the home Talos cluster was replaced by k3s (archive).

The llm group is dormant (commented out in inventory.yml).

Playbook Phases

site.yml groups roles into four commented phases. Tags cut across them — use just apply-tags <tag> to target a subset.

PhaseRolesMain tags
1 — System + packages + dotfilessudo, sshd, apk_packages, homebrew, termux_packages, bitwarden, shell_fonts, shell_dotfiles, omp, hive_ops, git, neovimsystem, packages, dotfiles
2 — Secrets + authshell_atuin, shell_ai, ssh_keys, ssh_mesh, github, tailscale, kube, forgejo_registrysecrets
3 — Desktop appsflatpak, bluefin_common, gnome, zen_browser (+ browser_fxa), pipewire_audiodesktop
4 — Servicessyncthing, systemd, bst_dashboard, kirocrew, proxy, tailscale_cert, server_hardeningservices

Only the secrets-tagged work needs Bitwarden. With the vault locked (or --skip-tags secrets), phases 1, 3 and 4 run normally and BW-touching tasks skip cleanly.