Fix some example command line options, add some more links to home page.

This commit is contained in:
Michael DeHaan 2012-03-11 21:46:05 -04:00
commit e726b9796d
7 changed files with 17 additions and 17 deletions

View file

@ -40,7 +40,7 @@ optionally use them as template sources.
To just transfer a file directly to many different servers::
ansible atlanta copy -a "/etc/hosts /tmp/hosts"
ansible atlanta -m copy -a "/etc/hosts /tmp/hosts"
To use templating, first run the setup module to put the template
variables you would like to use on the remote host. Then use the
@ -119,7 +119,7 @@ to poll, it looks like this::
If you do decide you want to check on the job status later, you can::
ansible all -n job_status -a jid=123456789
ansible all -m async_status -a "jid=123456789"
Polling is built-in and looks like this::

View file

@ -25,13 +25,13 @@ For comparison, Puppet and Chef have about 60k lines of code.
Ansible's core is a little over 1000 lines.
Ansible isn't just for configuration -- it's also great for Ad-Hoc
tasks, quickly firing off commands against nodes. Where Ansible
excels though, is expressing complex multi-node deployment processes,
executing complex sequences of commands on different hosts through
:doc:`playbooks`.
tasks, quickly firing off commands against nodes. See :doc:`examples`.
Where Ansible excels though, is expressing complex multi-node
deployment processes, executing complex sequences of commands on
different hosts through :doc:`playbooks`.
Extending ansible does not require programming in any particular
language -- you can write modules as scripts or programs that return
language -- you can write :doc:`modules` as scripts or programs that return
simple JSON. It's also trivially easy to just execute useful shell
commands.