Skip to content
Dotfiles logoDotfiles

New Machine Checklist

A clean, end-to-end walkthrough for setting up a new machine.

  1. Clone dotfiles to ~/.config/dotfiles.

  2. If you want private dotfiles, confirm gh auth status works before dot init; init clones dotfiles-private to ~/.config/dotfiles-private automatically when auth is available.

  3. Install bootstrap build prerequisites:

    Install bootstrap prerequisites
    yay -S --needed git mise

  4. Build the dot binary (mise trusts and installs the pinned toolchain, then the build task installs dependencies and compiles it):

    Build dot
    cd ~/.config/dotfiles
    mise trust
    mise install
    mise run dot:build

  5. Run first-use setup using the mode that matches this machine.

  6. UWSM, Hyprland, and Ghostty customisations are stowed from their public packages. Init removes only the retired timmo001/omarchy-uwsm checkout before linking the Quattro-compatible override.

  7. dot init verifies the pinned public package signing fingerprint, registers the signed timmo repository before the standard repositories, and retains AUR as the fallback for packages not published there.

  8. dot init opens the managed firewall rules (KDE Connect, Home Assistant, the OpenCode server, LocalSend, and the libvirt NAT network) when ufw is installed.

  9. Restart your shell and confirm dot help is on PATH.

  10. Run dot git-diff and verify the expected repo state.

  11. Reboot so the Omarchy session picks up OMARCHY_HOST, then run dot doctor to verify the setup. Use dot update for ongoing sync, stow refreshes, and rebuilds.

First-use setup
~/.config/dotfiles/scripts/.local/bin/dot init --noninteractive

--noninteractive skips the Hypr host questionnaire; elevation and package tools may still prompt. The accepted --confirm compatibility flag does not suppress those prompts.