cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
No description
8712 commits 47 branches 390 tags 440 MiB
Python 88.4%
PowerShell 7.5%
Shell 2%
C# 1.9%
Makefile 0.1%
Find a file
James Cammarata faa645c834 Merge pull request #6001 from jimi-c/issue_4087_sanitize_output 
Filter out messages that match the pattern username:password@host
2014-02-14 09:54:05 -06:00
bin More site rename things. 2014-01-28 20:29:42 -05:00
docs/man Updated footer date and adding in misc. file generated by earlier doc update 2014-02-12 16:14:41 -06:00
docsite Updated footer date and adding in misc. file generated by earlier doc update 2014-02-12 16:14:41 -06:00
examples Fix typos in ISSUE_TEMPLATE.md 2014-02-10 21:41:31 +00:00
hacking Allow hacking/env-setup module path to use config file library path 2014-02-12 12:06:57 +10:00
lib/ansible Merge pull request #6001 from jimi-c/issue_4087_sanitize_output 2014-02-14 09:54:05 -06:00
library Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier. 2014-02-13 18:28:29 -05:00
packaging Fix spec changelog date again 2014-02-13 10:06:09 -05:00
plugins Save api id to index as an int instead of a list 2014-02-09 16:33:34 +00:00
test Add the start of an integration test structure using Ansible playbooks, also added an assert action plugin to make writing those easier. 2014-02-13 18:28:29 -05:00
tests_new Remove fixme and extraneous file. 2014-02-13 18:31:30 -05:00
.gitignore Further modifications to the module formatter to adjust to the new theme, and some misc docs text corrections. 2013-12-25 13:24:29 -05:00
CHANGELOG.md Update CHANGELOG.md 2014-02-13 19:49:46 -05:00
CODING_GUIDELINES.md Fix various typos in markdown documentation 2014-02-10 23:00:19 +00:00
CONTRIBUTING.md Update bug reporting instructions to refer to the issue template 2014-02-11 10:26:25 -05:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile Remove man3 stuff since this is available via ansible-doc, rpm target should 2014-01-03 11:06:45 -05:00
MANIFEST.in Add some docs/examples 2012-08-14 13:05:44 -04:00
README.md AnsibleWorks -> Ansible 2014-01-28 20:29:42 -05:00
RELEASES.txt Updating documentation for release 1.4.5 2014-02-12 15:46:05 -06:00
setup.py AnsibleWorks -> Ansible 2014-01-28 20:29:42 -05:00
VERSION Version bump for 1.5 2013-11-21 16:33:23 -05:00

README.md

PyPI version

Ansible

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

Read the documentation and more at http://ansible.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 here for a variety of platforms. If you want a tarball of the last release, go to releases.ansible.com and you can also install with pip.

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

  • Read Contributing.md for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible.
  • When submitting a bug report, include 1) the output of 'ansible --version', 2) what you expected to happen, 3) what actually happened, and 4) any relevant commands and output.
  • All code submissions are done through pull requests. Take care to make sure no merge commits are in the submission, and use "git rebase" vs "git merge" for this reason. If submitting a large code change (other than modules), it's probably a good idea to join ansible-devel and talk about what you would like to do or add first and to avoid duplicate efforts. This not only helps everyone know what's going on, it also helps save time and effort if we decide some changes are needed.
  • irc.freenode.net: #ansible

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@ansible.com

Ansible, Inc