I have the seen the light, and the light spelled "Ansible".
All of my dotfiles should eventually be specified using an Ansible playbook, and with Ansible roles for each part of my configuration. This will make using my dotfiles even more of a "1 click installation" experience, since Ansible is able to install packages (for both apt and pacman), make sure directories exist, create symlinks, deploy templates, specify everything using variables, conditional execution of tasks, etc. That is awesome.
[x] Create an Ansible playbook that performs some simple task, such as downloading and symlinking wallpapers. (bccf60d821907e02e1042662803cf5cc2cda8695)
[ ] Move each part of my current configuration over to Ansible.
[x] alacritty (#9)
[x] bspwm (#17)
[x] emacs (#18)
[x] git (#19)
[ ] login
[ ] neovim
[ ] polybar
[ ] scripts -- this will probably disappear, and have scripts relating to other parts of my configuration to be parts of their respective roles, e.g. bspc-move-node will be a part of the bspwm roles.
I have the seen the light, and the light spelled "Ansible".
All of my dotfiles should eventually be specified using an Ansible playbook, and with Ansible roles for each part of my configuration. This will make using my dotfiles even more of a "1 click installation" experience, since Ansible is able to install packages (for both
apt
andpacman
), make sure directories exist, create symlinks, deploy templates, specify everything using variables, conditional execution of tasks, etc. That is awesome.alacritty
(#9)bspwm
(#17)emacs
(#18)git
(#19)login
neovim
polybar
scripts
-- this will probably disappear, and have scripts relating to other parts of my configuration to be parts of their respective roles, e.g.bspc-move-node
will be a part of thebspwm
roles.shell
-- should be renamed tozsh
ssh
sxhkd
tmux
xorg
zathura