Name Mode Size
..
apt 100755 6 kb
apt_repository 100755 2 kb
assemble 100755 3 kb
async_status 100755 2 kb
async_wrapper 100755 6 kb
authorized_key 100755 4 kb
command 100755 4 kb
copy 100755 3 kb
easy_install 100755 3 kb
facter 100755 1 kb
fetch 100755 0 kb
file 100755 11 kb
get_url 100755 6 kb
git 100755 6 kb
group 100755 4 kb
lineinfile 100755 4 kb
mount 100755 8 kb
mysql_db 100755 4 kb
mysql_user 100755 9 kb
nagios 100755 24 kb
ohai 100755 1 kb
ping 100755 1 kb
pip 100755 5 kb
postgresql_db 100755 4 kb
postgresql_user 100755 9 kb
raw 100755 0 kb
seboolean 100755 6 kb
selinux 100755 5 kb
service 100755 9 kb
setup 100755 28 kb
shell 100755 0 kb
slurp 100755 1 kb
subversion 100755 5 kb
supervisorctl 100755 3 kb
template 100755 0 kb
user 100755 11 kb
virt 100755 10 kb
wait_for 100755 2 kb
yum 100755 16 kb
README.md
Ansible ======= Ansible is a radically simple configuration-management, deployment, task-execution, and multinode orchestration framework. Read the documentation 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 ============ * [ansible-project mailing list](http://groups.google.com/group/ansible-project) * irc.freenode.net: #ansible Branch Info =========== * Releases are named after Van Halen songs. * The devel branch corresponds to release 0.7, "Panama". * Various release-X.Y branches exist for previous releases * All feature work happens on the development branch. * Major bug fixes will be made to the last release branch only * See CHANGELOG.md for release notes to track each release. 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 also be submitted to "ansible/release-X.Y" for the last release * Make sure "make tests" passes before submitting any requests. * Bonus points: * Joining the mailing list * Fixing bugs instead of sending bug reports. * 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 'release' 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](http://michaeldehaan.net/)