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
8452 commits 10 branches 167 tags 272 MiB
Python 99.5%
Shell 0.3%
HCL 0.1%
Find a file
Michael DeHaan 81e9a60589 Much rejoicing, ansibleworks.com is now ansible.com 
Also note AWX is named "Tower" now, as we found that simpler.
2014-01-28 20:29:41 -05:00
bin Adding an "Example Playbook" section to the README template for ansible-galaxy 2014-01-24 15:39:30 -06:00
docs/man Add skip_tags to ansible-playbook man page 2014-01-27 18:03:10 -05:00
docsite Much rejoicing, ansibleworks.com is now ansible.com 2014-01-28 20:29:41 -05:00
examples Added ANSIBLE_SSH_PIPELINING option to enable/disable pipelining support 2014-01-16 12:41:33 -06:00
hacking Add an "all" category so all modules show up uncategorized there. 2014-01-02 17:42:18 -05:00
lib/ansible Fix .ssh/known_hosts path expansion. 2014-01-28 15:11:44 -06:00
library Tested implementation adding action option for (add, delete, unique). 2014-01-28 20:29:41 -05:00
packaging Remove man3 stuff since this is available via ansible-doc, rpm target should 2014-01-03 11:06:45 -05:00
plugins update default EC2 exclude regions -- this should be the best configuration for most users, but some may still want to tweak. 2014-01-19 13:13:43 -05:00
test Merge pull request #5337 from bob-smith/bugfixFQDNParsing 2014-01-14 08:28:38 -08: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 Fix git module parameters to conform to code standards 2014-01-23 16:44:17 -05:00
CODING_GUIDELINES.md Missing colon. 2014-01-26 17:06:32 -05:00
CONTRIBUTING.md Add note for more mailing list info 2014-01-15 11:17:08 +01: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 Update README.md 2013-12-15 11:50:18 -05:00
RELEASES.txt Add release history for 1.4.1 into 1.5 branch. 2013-11-27 18:41:07 -05:00
setup.py setup.py: fix ansible-galaxy was not installed when using make install 2013-12-20 09:27:13 +01: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://ansibleworks.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 http://ansibleworks.com/releases/ 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@ansibleworks.com

AnsibleWorks