.dotfiles

Personal dotfiles. ubuntu / macos / tmux / neovim. single command install.

Dependencies:

• ubuntu: sudo apt install -yq make ansible
• macos: brew install ansible (make comes with the Command Line Tools), plus homebrew itself

make installs ansible and the required collections for you if they are missing.

install locally

inventory/local.ini should have something like:

[local]
localhost ansible_connection=local

Then you can install with:

make full

./ansible.cfg loads everything in ./inventory/, so drop additional inventory files in there for remote targets.

optional topics

llvm, java and ghidra are tagged never, so a normal run skips them. Ask for them by name:

make install TAGS=llvm,ghidra   # everything, plus those two
make install TOPICS=ghidra      # only ghidra, skipping everything else

TOPICS is the useful one for adding a tool to a box that is already set up - it takes seconds instead of re-running the whole playbook. Fact gathering and the per-OS vars are tagged always, so a single-topic run still has everything it needs. On ubuntu the ghidra tag pulls in java too, since that ghidra needs a jdk.

layout

playbook.yaml gathers facts, loads vars/<os_family>.yaml and then hands off to tasks/<os_family>/main.yaml, which lists the topics that apply to that platform in order. Task files therefore never branch on the OS:

vars/Debian.yaml      package lists + paths for ubuntu
vars/Darwin.yaml      package lists + paths for macos
tasks/Debian/         apt, source builds, X11 dotfiles
tasks/Darwin/         homebrew
tasks/common/         works as-is on both (dotfiles, git, ssh, rust, ...)

Adding a platform means a vars/<os_family>.yaml and a tasks/<os_family>/main.yaml; anything a topic cannot support there is simply left out of that main.yaml.

docker

A docker image has been provided - mostly this is just to validate the dotfiles inside a 'clean' environment but it is useable if a docker dev env is your thing:

docker run --rm -ti pemcconnell/dev:master