Hi Kai,
Thank you for your feedback.
On 03-08-16 09:44, Kai Stian Olstad wrote:
On 01.08.2016 18:56, Patrick Laimbock wrote:
Hi,
Ansible 2.1.1.0.
Situation: Tim and Bob both deploy servers. Tim checks out the central
ansible git repo to /home/tim/ansible while Bob checks it out to
/home/bob/ansible. No special ansible.cfg is used by either.
This is a very common way to do it.
You can also put the ansible.cfg in this folder so everybody shares the
same ansible.cfg.
Got it.
Problem: paths differ (/home/tim/ansible vs /home/bob/ansible) so you
can not use static paths in the playbooks etc.
This is not a problem you always use relative paths and not
absolute(static) path.
Great.
Question: how do you solve that? How do you specify something like a
base_dir variable which is read early on so that all static paths can
be replaced.
Relative path and Ansible has a directory layout that it understand, I
recommend reading this page that explain the concept.
https://docs.ansible.com/ansible/playbooks_best_practices.html
Will read that.
So when you run ansible or ansible-playbook Tim and Bob will always run
them from within ~/ansible
[snip]
>
It looks like a very strange concept, I do recommend picking up a
Ansible book to get basic knowledge of how Ansible works.
The concept is sorta used by the Fedora Infrastructure team. Looking at
their setup I wondered about defining paths via vars hence my question
to the list.
Thanks again for your help!
Best,
Patrick
--
You received this message because you are subscribed to the Google Groups "Ansible
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/996bab8a-2a40-cc3e-09db-0eb11e7bc8e2%40laimbock.com.
For more options, visit https://groups.google.com/d/optout.
