VM Test Plan & Decisions

VM Test Plan

Phase 1: Base Install

  • Create VM (QEMU/libvirt, 4 CPU, 8GB RAM, 60GB disk)

  • Install Arch Linux (archinstall or manual)

  • Configure user, sudo, networking

  • Install yay (AUR helper)

Phase 2: Tier 1 Bootstrap

  • Install system packages

  • Clone dots-quantum, stow essential packages

  • Clone domus-nvim, verify plugins install

  • Import secrets (SSH, GPG, gopass)

  • Verify: shell prompt, git push/pull, nvim opens clean

Phase 3: Tier 2 Verification

  • Clone documentation repos

  • Run make serve in domus-docs — site builds

  • Clone active project repos

  • Stow remaining packages

  • Verify: tmux sessions, lazygit, full workflow

Phase 4: Script It

  • Write bootstrap script from validated steps

  • Test script on fresh VM

  • Document in domus-infra-ops runbook

Decisions Needed

  1. Keep all 38 tmuxinator templates or prune?

    Many reference dead paths. Audit against active repos before migrating.

  2. Machine-specific configs (monitors, GPU)?

    dots-quantum/hosts/ directory handles this. Need a new hostname entry for the VM and the target machine.

  3. Where to host the bootstrap script?

    Options: dots-quantum/setup (existing), domus-infra-ops runbook, or standalone repo.

  4. Gopass store migration?

    Clone from Gitea remote, or restore from backup? Test both paths in VM.