You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
Chris Read dbb4afff50 Use the /Users/cread env var instead of hard coding /home/<username> 13 years ago
bin Unused imports 13 years ago
docs/man Fix man page option description indentation. 13 years ago
examples Add another example to file_secontext.yml 13 years ago
hacking Make it possible to use facts from hosts in templates for other hosts. 13 years ago
lib/ansible Use the /Users/cread env var instead of hard coding /home/<username> 13 years ago
library Fix bug in library/file 13 years ago
packaging Version bump for 0.3 release 13 years ago
test Fix bug in src. Should not code this early :) 13 years ago
.gitignore clean exec bits from lib/ansible/*.py, ignore Eclipse/PyDev files 13 years ago
COPYING license file should be in source tree 13 years ago
MANIFEST.in Move setup.py stuff back to top level as "make sdist" was not working, plus, it makes sources cleaner. 13 years ago
Makefile debian packaging 13 years ago
README.md Update README to indicate new branch name 13 years ago
VERSION Version bump for 0.3 release 13 years ago
setup.py Add requirements in setup.py. 13 years ago

README.md

Ansible

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

Read all about at it at (http://ansible.github.com)

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

Patch Instructions

Contributions to the core and modules are greatly welcome.

  • Required Process:
    • Submit github pull requests to the "ansible/devel" branch for features
    • Fixes for bugs may be submitted to "ansible/master"
    • Make sure "make tests" passes before submitting any requests.
  • Bonus points:
    • Joining the mailing list
    • Using squash merges
    • Updating the "rst/*" files in the docs project and "docs/" manpage content
    • Adding more unit tests
  • Avoid:
    • Sending patches to the mailing list directly.
    • Sending feature pull requests to the 'master' branch instead of the devel branch
    • Sending pull requests to mpdehaan's personal ansible fork.

Author

Michael DeHaan -- michael.dehaan@gmail.com

http://michaeldehaan.net