Salt
1da2e625b5
This seems like a bad idea at first, but then you realize that the moment a user's .xsessionrc or .xinitrc gets sourced in, 99% of the time they exec themselves |
||
---|---|---|
.templates | ||
inventory | ||
playbooks | ||
roles | ||
.gitignore | ||
ansible-pull.cfg | ||
ansible.cfg | ||
localhost-deploy.sh | ||
provision.yml | ||
README.md | ||
site.yml |
Salt's Ansible Scripts
A collection of Ansible scripts to manage all of my machines.
Quickstart
To quickly get a machine up and running, add it to the inventory, role it out, and ./provision.yml
it. The playbook assures a sane running environment and then sets up ansible-pull on a timer that immediately triggers. Leave it be, come back 10 minutes later and polish it up as required.
Overview
The main playbook, site.yml
, can be separated into more or less two parts:
-
The home machine half, tied together via Zerotier
-
The 9iron half, with public IPs and resolvable names
See inventory/hosts.yml
for details on what machines have what roles and what configuration. I try my best to make self-explaning configuration, so everything should mostly make sense on a first read. If you have any questions, hit me up.
Your Roles are Trash
I know. Please file an issue.