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
8004 commits 10 branches 167 tags 272 MiB
Python 99.5%
Shell 0.3%
HCL 0.1%
Find a file
Roger López a3dcac0a0f django_manage need not require virtualenv in PATH 
The virtualenv parameter to the django_manage command is used to locate
the virtualenv and build it if necessary.  Access to the virtualenv
executable is only needed if the virtualenv directory doesn't exist and
needs to be built.  This patch allows for the situation where a
virtualenv that is not in the PATH was used to create a virtualenv prior
to running the django_manage module.
2013-12-17 14:45:42 -05:00
bin Merge pull request #4817 from j2sol/zero-exit 2013-12-02 10:04:18 -08:00
docs/man Add release history for 1.4.1 into 1.5 branch. 2013-11-27 18:41:07 -05:00
docsite fixed a reference to AWX site 2013-12-15 13:12:20 +02:00
examples Lookup plugin for etcd 2013-10-24 21:28:48 +02:00
hacking env-setup fix for zsh <= 4.3.10 2013-12-04 14:36:47 +01:00
lib/ansible Merge pull request #5259 from mvo5/bugfix/improve-error-on-invalid-vars-file 2013-12-17 11:12:53 -08:00
library django_manage need not require virtualenv in PATH 2013-12-17 14:45:42 -05:00
packaging Merge #4689 from dirtyharrycallahan/ansible 2013-12-04 15:59:01 -05:00
plugins Fix loading from cache in ec2.py inventory plugin. 2013-12-05 21:33:25 -08:00
test Ensure test_command tests are actually correct 2013-12-03 12:03:39 +10:00
.gitignore Update the .gitignore based on the docsite restructuring. 2013-11-27 21:35:43 -05:00
CHANGELOG.md Addresses #5276 update documentation for ec2_ami no_reboot parameter 2013-12-12 18:03:00 -05:00
CONTRIBUTING.md Update CONTRIBUTING.md 2013-12-15 11:53:54 -05:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
Makefile fix make tests to use the set of module from git checkout 2013-11-16 12:45:24 +01: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 Revert "Merge pull request #4874 from leth/editable_install" 2013-12-16 15:57:03 -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://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