Go to file
Matt Lesko b37ecb055c set checkout destination directory to be full path
we chdir into this path and read the playbook/inventory if a
non-absolute path is given on the command line, that will fail
2013-07-05 17:57:01 +00:00
bin set checkout destination directory to be full path 2013-07-05 17:57:01 +00:00
docs/man Merge pull request #3094 from sfromm/issue2464-redux 2013-06-03 09:01:39 -07:00
docsite Document 'smart' option and connection type default changes. 2013-07-04 19:10:56 -04:00
examples Default to 'smart' transport, which will use OpenSSH if it can support ControlPersist. 2013-07-04 16:47:17 -04:00
hacking Fixes #3294 2013-06-30 19:59:48 -04:00
lib/ansible Improve interlaced output prevention when asking for host key approval. 2013-07-04 18:17:45 -04:00
library Revert "ini_file: add support for lists of options/values" 2013-07-05 12:04:07 -04:00
packaging Update packaging changelogs. 2013-07-04 21:58:05 -04:00
plugins Merge pull request #3357 from neomantra/devel 2013-06-30 14:20:21 -07:00
test expanduser on each component of plug-in paths 2013-06-22 17:01:12 -05:00
.gitignore Update .gitignore 2013-06-10 15:46:16 -04:00
CHANGELOG.md Merge in release notes from 1.2.1 2013-07-04 22:02:10 -04:00
CONTRIBUTING.md Add a line about testing. 2013-02-23 12:41:00 -05:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Do not set RPMDIST to '%dist' when dist is not set by the distribution. 2013-06-02 13:27:04 -04:00
MANIFEST.in Add some docs/examples 2012-08-14 13:05:44 -04:00
README.md Use new site URLs in README 2013-06-17 22:20:31 -06:00
RELEASES.txt Update the releases list. 2013-07-04 21:54:58 -04:00
setup.py fix package mentioned twice in setup.py 2013-05-15 21:02:53 +02:00
VERSION Version bump and assorted things to start new development version. 2013-06-10 15:34:52 -04:00

Ansible

Ansible is a radically simple configuration-management, deployment, task-execution, and multinode orchestration framework.

Read the documentation and more at http://ansibleworks.com/

Many users run straight from the development branch (it's generally fine to do so), but you might also wish to consume a release. You can find instructions on http://ansibleworks.com/docs/gettingstarted.html for a variety of platforms. If you want a tarball of the last release, go to http://ansibleworks.com/releases/ and you can also install with pip (though that will bring in some optional binary dependencies you normally do not need).

Design Principles

  • Dead simple setup
  • Super fast & parallel by default
  • No server or client daemons; use existing SSHd
  • No additional software required on client boxes
  • Modules can be written in ANY language
  • Awesome API for creating very powerful distributed scripts
  • Be usable as non-root
  • The easiest config management system to use, ever.

Get Involved

Branch Info

  • Releases are named after Van Halen songs.
  • The devel branch corresponds to the release actively under development.
  • Various release-X.Y branches exist for previous releases
  • We'd love to have your contributions, read "CONTRIBUTING.md" for process notes.

Author

Michael DeHaan -- michael@ansibleworks.com

AnsibleWorks