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

Jeroen Hoekx 029fe1273c Modify /usr/bin/ansible and playbooks to use the new async API.		13 years ago
bin	Modify /usr/bin/ansible and playbooks to use the new async API.	13 years ago
docs/man	Because paramiko using a pty can't distinguish stderr and stdout, remove handling that	13 years ago
examples	Revert "Revert "Actually wait for password prompt in remote sudo execution. Totally breaks stderr debugging"	13 years ago
hacking	Clarify that stderr WILL crash your module. Can't redirect because if we do we lose tracebacks	13 years ago
lib/ansible	Modify /usr/bin/ansible and playbooks to use the new async API.	13 years ago
library	Make async wrapper kill the process it supervises.	13 years ago
packaging	Version bump for 0.3 release	13 years ago
test	Modify /usr/bin/ansible and playbooks to use the new async API.	13 years ago
.gitignore	clean exec bits from lib/ansible/*.py, ignore Eclipse/PyDev files	13 years ago
CHANGELOG.md	changelog update	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	changelog and readme	13 years ago
VERSION	Version bump for integration branch (soon to be renamed 'devel'), didn't update package	13 years ago
setup.py	Add requirements in setup.py.	13 years ago

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

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.