ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity
Mirror of https://github.com/ansible-collections/community.general.git
5160 commits 10 branches 167 tags 272 MiB
Python 99.5%
Shell 0.3%
HCL 0.1%
Find a file
lwade 07a1b2f1c1 Start of aws best practices docs
2013-05-24 16:59:24 +01:00
bin Fix empty requirements specifications in modules documentation 2013-05-16 17:15:21 +02:00
docs/man Update release version. 2013-04-02 20:48:30 -04:00
docsite Start of aws best practices docs 2013-05-24 16:59:24 +01:00
examples Add version added field to notification modules. 2013-05-11 16:36:37 -04:00
hacking Fixup the module formatter to explain the EXAMPLES string as well. 2013-05-11 16:32:22 -04:00
lib/ansible Prefer categorized modules to uncategorized, such that if someone does an install on top of old content 2013-05-19 20:09:44 -04:00
library Fixed handling of urlopen result to work properly under both python 2.4 and python 2.6 2013-05-21 13:59:42 -04:00
packaging update archlinux PKGBUILD for pacman 4.1 2013-05-15 12:57:42 -05:00
plugins Do not need to chmod cache file each time 2013-05-21 14:44:00 -07:00
test Dealing with invalid symlinks and symlink permissions 2013-05-09 15:35:05 -04:00
.gitignore Add vim swap files to gitignore 2013-05-18 21:51:43 +01:00
CHANGELOG.md update changelog. 2013-05-11 15:49:44 -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 make path to nosetests executable configurable 2013-05-11 13:16:04 +03:00
MANIFEST.in Add some docs/examples 2012-08-14 13:05:44 -04:00
README.md Update README.md 2013-04-06 17:22:21 -03:00
RELEASES.txt Update the release date & code names in the releases file. 2013-04-20 18:21:25 -04:00
setup.py fix package mentioned twice in setup.py 2013-05-15 21:02:53 +02:00
VERSION Update release version. 2013-04-02 20:48:30 -04:00

README.md

Ansible

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

Read the documentation and more at http://ansible.cc

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://ansible.cc/docs/gettingstarted.html for a variety of platforms. If you want a tarball of the last release, go to http://ansible.cc/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