From 84eb0d972c4751844895523f7805a562e8506ca7 Mon Sep 17 00:00:00 2001 From: Gilles Cornu Date: Tue, 25 Feb 2014 06:57:10 +0100 Subject: [PATCH] Ansible Docs: Tip to ship a local `ansible.cfg` Hint motivated by misleading situations reported in #2302. --- website/docs/source/v2/provisioning/ansible.html.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/website/docs/source/v2/provisioning/ansible.html.md b/website/docs/source/v2/provisioning/ansible.html.md index 4c2b09950..868258c02 100644 --- a/website/docs/source/v2/provisioning/ansible.html.md +++ b/website/docs/source/v2/provisioning/ansible.html.md @@ -217,4 +217,12 @@ Vagrant is designed to provision [multi-machine environments](/v2/multi-machine) ansible.limit = 'all' end end -``` \ No newline at end of file +``` + +### Provide a local `ansible.cfg` file + +Certain settings in Ansible are (only) adjustable via a [configuration file](http://docs.ansible.com/intro_configuration.html), and you might want to ship such a file in your Vagrant project. + +As `ansible-playbook` command looks for local [`ansible.cfg`] configuration file in its *current directory* (but not in the directory that contains the main playbook), you have to store this file adjacent to your Vagrantfile. + +Note that it is also possible to reference an Ansible configuration file via `ANSIBLE_CONFIG` environment variable, if you want to be flexible about the location of this file.