From 300be75664d90191596fa3b62a1ba163c7b6b649 Mon Sep 17 00:00:00 2001 From: Chl Date: Sat, 18 Jan 2020 18:26:08 +0100 Subject: [PATCH] readme: little review --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c10b4be..5e30d7f 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ Only tested on Debian 10 amd64 so far, with Ansible 2.7.7. Note : to test or to limit to one particular host : ``` ansible foo.bar.com -m ping -ansible-playbook -l foo.bar.com -C -D site.yml +ansible-playbook -l foo.bar.com -v -C -D site.yml ``` ## Directory layout @@ -31,7 +31,7 @@ ansible-playbook -l foo.bar.com -C -D site.yml We follow (more or less) the recommendations of https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html with : -- `site.yml` : *master playbook* +- `site.yml` : master playbook - `ansible.cfg` and `inventory` : the first one set up some default configurations and introduce the second one : the inventory. - `roles/common/`, `roles/fooapp/` : the roles with their tree `tasks/main.yml`, `files/`, `handlers/main.yml`, ... - `group_vars/group1.yml` and `host_vars/hostname1.yml` : variables dedicated to a group or a host respectively. @@ -45,5 +45,5 @@ adapt. - stop execution if host is running an untested system ? - use jenkins-cli to maintain credentials.xml ? It's not really easy to manipulate in Ansible at the moment... +- lookup more throroughfully at [configuration as code plugin](https://plugins.jenkins.io/configuration-as-code/) - update plugins, or at least display a warning when they are not up to date. -- configure NginX