20 Commits (73dbab702f8469c8ce99ffc0e1d8da1d4fa82d62)

Author	SHA1	Message	Date
James Tanner	6b60267898	Document per task remote_user, based on #3932	11 years ago
Michael DeHaan	0cd09dd54f	Remove extra "latest/" subdirectory in docs build structure.	11 years ago
Michael DeHaan	26819d707d	Reorganize docs structure to support snapshots.	12 years ago
Michael DeHaan	148d8859ba	Docs on parameterized roles, make document generation output less noisy	12 years ago
Michael DeHaan	f9890c9973	Show other way to ignore command/shell errors	12 years ago
raphinou	ba2582fff6	replaced && by || ... In the example, you want /bin/true to be executed if the first command has an error return code. Combining command with && will run the second only if the first is successful. Combining them with ||, the second will be run only of the first fails, what is wanted here.	12 years ago
Michael DeHaan	518007a1ba	Fix version added attribute, update docs URL	12 years ago
michael@ansibleworks.com	e086d6fd89	Doc updates	12 years ago
Tim Gerla	242f988daf	Add links to the ansible-examples repository	12 years ago
Jim Kleckner	92844d3dcd	Minor spelling fixes	12 years ago
Michael DeHaan	3aceae57af	Fixup documentation formatting	12 years ago
Michael DeHaan	3422ae6737	Document how to do task includes using with_items and externalized data.	12 years ago
Michael DeHaan	d8a77c0468	Add some 1.1 feature documentation	12 years ago
Daniel Hokka Zakrisson	073fb21bcb	Document that task includes are now infinite depth	12 years ago
Dag Wieers	66fb7fd9de	Make use of yes/no booleans in playbooks ... At the moment Ansible prefers yes/no for module booleans, however booleans in playbooks are still using True/False, rather than yes/no. This changes modifies boolean uses in playbooks (and man pages) to favor yes/no rather than True/False. This change includes: - Adaptation of documentation and examples to favor yes/no - Modification to manpage output to favor yes/no (the docsite output already favors yes/no)	12 years ago
Serge van Ginderachter	d04bd04f80	typo in handlers example yaml	12 years ago
Nigel Metheringham	a457d24b97	Added comment about long lines in playbooks ... I had trouble finding this information, so though it was worth adding to docs... but am not sure its easy to find for someone specifically to find. At least I think this inclusion matches the tone of document, but maybe this info should go into a FAQ instead/as-well?	12 years ago
Michael DeHaan	0677891fc6	More docs	12 years ago
Philipp Grau	9b15b5d592	Use && for executing next command if, and only if, command1 returns an exit status of zero.	12 years ago
Michael DeHaan	d6e4b1bf5b	Subtree merge of ansible-docs	12 years ago