flyingscorpio/setup-cockpit
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
Personal dotfiles. The installation supports Arch and Debian based systems.
974 commits 1 branch 0 tags 8.6 MiB
Find a file
flyingscorpio@clevo 7ffb9f1ba5 Add meta-no-info in ansible-lint skip list
2022-06-25 18:49:30 +02:00
.config Add meta-no-info in ansible-lint skip list 2022-06-25 18:49:30 +02:00
roles Reload systemd daemon when protonvpn confs are updated 2022-06-22 20:47:45 +02:00
.gitignore Remove secrets file, not needed 2022-03-11 19:22:02 +01:00
.yamllint.yml Add default yamllint config 2022-06-25 14:12:53 +02:00
ansible.cfg Add stdout_callback option 2022-03-11 18:57:33 +01:00
get-vault-password.sh Add get-vault-password.sh script to avoid passing in cli 2022-02-26 10:05:07 +01:00
Makefile Hide echo from Make 2022-05-02 22:02:52 +02:00
playbook.yml Role neovim could be called vim 2022-06-12 12:29:21 +02:00
README.md Implement previous roles 2022-03-17 22:15:26 +01:00
todo Make mail for me underlined 2022-06-10 22:30:30 +02:00

README.md

setup-cockpit

My personal dotfiles managed with ansible.

The playbook playbook.yml contains all the things to install, each in a role with a tag so that it can be individually installed.

For convenience, a Makefile contains the ansible-playbook command that will use the tag specified to make:
So make vim will call ansible-playbook with the vim tag.

The Makefile also includes vault password, which is retrieved via password-store with the git-vault-password.sh script.

The roles called are logged to .roles_played. They can then be called again by make previous, for example to update the system according to the playbook.