How baslangenberg/dots works
Project type and purpose
• This is an Ansible-based dotfiles provisioning project. Its goal is to automate the setup of a personalized development environment (Arch-style on WSL2/Ubuntu or a Vagrant VM), installing configs for zsh, tmux, vim/neovim, polybar, ranger, etc.
• It includes testing via Molecule, supporting immutability and idempotence in the provisioning.
Analysis of the file structure
• Top-level:
• setup.yml: the main playbook
• Vagrantfile + bootstrap.sh + utils/: for spinning up and provisioning a VM
• roles/dots/: a single role encapsulating dotfiles, handlers, tasks, defaults, files, templates, meta
• molecule/: under roles to test the “dots” role via Docker or Vagrant
• config files: .gitignore, .pre-commit-config.yaml, yamllint.config.yaml
• roles/dots breakdown:
• defaults/main.yml: default variables (e.g. dotfile locations)
• tasks/*.yml: sequences to install packages, copy configuration files, run scripts
• files/: actual dotfiles (.gitconfig, .zshrc, init.lua for Neovim, etc.)
• handlers/main.yml: reload or restart services if needed (e.g. notify on config change)
• molecule/: scenario definitions for testing
• utils/: helper scripts for bootstrapping (ansible.sh, chroot.sh) and mirrorlist generation
• Windows/WSL specifics: caps2ctrl.reg, windows-terminal-settings.json, hosts