Add note in README about ad-hoc commands
Just because I keep forgetting the syntax lol
This commit is contained in:
parent
39f3b1f852
commit
d34844351b
10
README.md
10
README.md
@ -40,6 +40,16 @@ Adding a new server will require the following be fulfilled:
|
|||||||
|
|
||||||
From there, running the playbook `site.yml` should get the machine up to snuff. To automate the host-local steps, use the script file `contrib/bootstrap.sh`.
|
From there, running the playbook `site.yml` should get the machine up to snuff. To automate the host-local steps, use the script file `contrib/bootstrap.sh`.
|
||||||
|
|
||||||
|
## Ad-Hoc Commands
|
||||||
|
|
||||||
|
The inventory is configured to allow for ad-hoc commands with very little fuss. For example:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
ansible -m shell -a 'systemctl is-failed ansible-pull.service' all
|
||||||
|
```
|
||||||
|
|
||||||
|
These commands must be run from the root of the repo.
|
||||||
|
|
||||||
## Ansible Galaxy
|
## Ansible Galaxy
|
||||||
|
|
||||||
Several of the roles in this repository are sourced from Ansible Galaxy. They're mirrored here for both easy compatibility with `ansible-pull` and in case the sources go down. Despite this, they're still managed in `roles/requirements.yml` for ease of management, source tracking, and updating. Any forks or deviations from these sources should be thoroughly documented.
|
Several of the roles in this repository are sourced from Ansible Galaxy. They're mirrored here for both easy compatibility with `ansible-pull` and in case the sources go down. Despite this, they're still managed in `roles/requirements.yml` for ease of management, source tracking, and updating. Any forks or deviations from these sources should be thoroughly documented.
|
||||||
|
Loading…
Reference in New Issue
Block a user