mirror of https://github.com/ansible/ansible.git
Mirror of https://github.com/ansible/ansible.git
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.
ec7c8eb8ca
With this patch one can do `make rpm` and get an RPM file that looks like: rpm-build/noarch/ansible-0.6-0.git201208010541.el6.noarch.rpm My goal was not to rewrite the original SPEC file, and/or the tarball. In other projects what I tend to do is prepare the SPEC file in the tarball with the correct version/release so that rpmbuild works on the (released) tarball as well. If this is wanted, we will have to rewrite the SPEC file on the fly as part of creating the tarball. If there is no git or .git/ available, we will use the current time. |
12 years ago | |
---|---|---|
bin | 12 years ago | |
docs/man | ||
examples | 12 years ago | |
hacking | 12 years ago | |
lib/ansible | 12 years ago | |
library | 12 years ago | |
packaging | ||
test | 12 years ago | |
.gitignore | ||
CHANGELOG.md | 12 years ago | |
COPYING | ||
MANIFEST.in | ||
Makefile | 12 years ago | |
README.md | ||
VERSION | ||
setup.py |
README.md
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
- 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
- ansible-project mailing list
- irc.freenode.net: #ansible
Branch Info
- Releases are named after Van Halen songs.
- The master branch corresponds to release 0.5 "Amsterdam".
- The devel branch corresponds to release 0.6 "Cabo".
- All feature work happens on the development branch.
- Major bug fixes will be made to the master branch, but not minor ones.
- See CHANGELOG.md for release notes to track each release.
Patch Instructions
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
- Fixing bugs instead of sending bug reports.
- 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.
Author
Michael DeHaan -- michael.dehaan@gmail.com