omarchy-dotfiles

My Omarchy config, synced across machines. No symlinks, no templating engine — just rsync + git behind a small bash script.

Why not stow or chezmoi

• Stow (what the Omarchy manual suggests) uses symlinks. Omarchy's update migrations run sed -i, which replaces a symlink with a regular file and silently detaches it from the repo. See omarchy#191.
• chezmoi (what the community mostly uses) is fine but its value is Go templating, which I don't want.

This keeps real files in $HOME where Omarchy expects them. When an update rewrites one, it shows up as ordinary drift you review with dots diff.

Usage

./dots status          # what differs between $HOME and this repo
./dots diff [path]     # unified diff
./dots pull            # $HOME  -> repo   (capture local changes)
./dots apply           # repo   -> $HOME  (backs up first, prompts)
./dots sync "message"  # pull + themes save + commit + push

./dots track <path>            # start tracking (shared across machines)
./dots track --host <path>     # track per-machine (e.g. monitors.lua)
./dots untrack <path>

./dots themes save|install     # git-based themes, by URL (not contents)
./dots packages save|install   # explicit pacman + AUR package lists

Layout

manifest              tracked paths (relative to $HOME) + rsync excludes
home/                 shared files, mirrored tree
hosts/<hostname>/     per-machine overrides, applied *after* home/
themes.list           name <TAB> git URL
packages.list         pacman -Qqen
packages-aur.list     pacman -Qqem
packages-ignore.list  installed here, deliberately never recorded
packages-drivers.list globs for hardware-bound packages (see below)

hosts/<hostname>/ wins over home/ for the same path. Hostname comes from /etc/hostname.

What is deliberately NOT tracked

• Files byte-identical to Omarchy's defaults in /usr/share/omarchy/config/. Committing those pins you to today's defaults and reverts upstream improvements on the next machine. Run dots track <path> once you change one.
• Theme contents. The four installed themes are upstream git clones totalling ~188 MB. themes.list records their URLs; dots themes install re-clones.
• Microcode and per-vendor GPU drivers, unless the host asks for them. The next machine wants the drivers for its GPU, so packages-drivers.list keeps them out of the shared list and out of doctor's "installed but not recorded". A host opts in by naming one in hosts/<hostname>/packages.list; from then on its driver set is tracked and packages save keeps it there.
• Sockets, logs, and runtime state (*.sock, session.json, .plugins.lock).
• Secrets. Nothing here should contain credentials — check before committing.

New machine

# install Omarchy first, then:
git clone ssh://forgejo@git.lyte.dev/lytedev/omarchy-dotfiles.git ~/Projects/omarchy-dotfiles
ln -sfT ~/Projects/omarchy-dotfiles ~/.config/omarchy-dotfiles   # optional convenience
cd ~/Projects/omarchy-dotfiles
./dots packages install     # optional
./dots themes install
./dots apply

The clone can live anywhere; dots resolves its own directory, so running it through the ~/.config symlink works and still writes to the real path.

hyprctl reload && hyprctl configerrors
omarchy restart shell
omarchy restart terminal

Per-machine files land in hosts/<new-hostname>/ — copy from another host's directory and edit, e.g. monitors.lua.

After an omarchy update

./dots status     # see what the migrations rewrote
./dots diff       # inspect
./dots pull       # accept upstream's version into the repo
# ...or ./dots apply to force your version back