shaba/awx
1
0
Fork 0
mirror of https://github.com/ansible/awx.git synced 2024-11-02 09:51:09 +03:00
Code Releases Activity
15,002 Commits 40 Branches 19 Tags 380 MiB
Python 97.7%
Jinja 0.9%
Makefile 0.5%
Shell 0.3%
HTML 0.2%
Other 0.2%
46287f6923
Go to file
Steininger Robert, IR 46287f6923 proxy settings default omit
2017-09-28 10:11:29 +02:00
.github extend api maintainers folder to main 2017-09-12 13:40:17 -04:00
awx Merge pull request #291 from Zokormazo/fix-const 2017-09-26 09:45:42 -04:00
config Implement alternate ports for nginx 2017-01-23 14:34:15 -05:00
docs Update mattermost notification docs with examples 2017-09-14 18:25:01 -07:00
installer proxy settings default omit 2017-09-28 10:11:29 +02:00
requirements bump azurerm dependencies to support Ansible 2.4 2017-09-01 15:15:53 -04:00
tools use dataset name as naming prefix 2017-09-15 17:22:13 -04:00
.coveragerc fixing ad_hoc imports 2016-02-01 18:37:56 -05:00
.dockerignore Use tower_devel as base image for unit tests 2016-11-11 15:47:17 -05:00
.dput.cf Add support for pbuilder chroot builds 2015-09-16 16:28:05 -04:00
.editorconfig Add models and select component 2017-06-12 09:53:11 -04:00
.env Add support for honcho as alternative to tmux for running development servers. 2015-08-04 15:26:27 -04:00
.gitignore Integrate a migration-detector middleware 2017-09-11 11:09:45 -04:00
.mini-dinstall.cf Add support for pbuilder chroot builds 2015-09-16 16:28:05 -04:00
.pylintrc [pylint] Additional paths to ignore 2015-02-06 09:47:41 -05:00
.travis.yml Be sure to install ansible 2016-07-22 13:19:57 -04:00
API_STANDARDS.md Start of guidelines around API development. 2014-06-17 13:52:57 -05:00
CONTRIBUTING.md Updating contributing for What should I work on? 2017-09-19 13:46:45 -04:00
DCO_1_1.md Updates CONTRIBUTING and README 2017-08-29 21:18:56 -04:00
INSTALL.md Clarify awx-logos location. Add 'docker' group note. 2017-09-25 09:48:59 -04:00
ISSUES.md Merge pull request #10 from wwitzel3/botdoc 2017-09-12 14:07:18 -04:00
LICENSE.md Rename LICENSE to LICENSE.md 2017-08-22 14:34:25 -04:00
Makefile omit old unit tests from "test" make target 2017-09-21 21:33:34 -04:00
manage.py fixed copyright date 2015-06-11 16:10:23 -04:00
MANIFEST.in Rename tower-python to awx-python 2017-07-25 13:31:52 -04:00
nodemon.json Rename packaging folder for node stuff 2015-07-27 10:19:15 -04:00
pytest.ini modularization of inventory_import command 2017-05-01 14:37:42 -04:00
README.md The link to the AWX project FAQ added 2017-09-09 11:19:56 +02:00
setup.cfg fix broken shippable test suite 2017-09-06 16:12:43 -07:00
setup.py - list the licence as Apache License 2.0 everywhere 2017-09-12 17:49:47 +03:00
shippable.yml only run shippable UI for devel and release branches 2017-08-18 14:21:48 -04:00
tox.ini replace PyCrypto usage w/ crytography; ansible no longer bundles it 2017-08-07 12:19:51 -04:00

README.md

Run Status

AWX

AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is the upstream project for Tower, a commercial derivative of AWX.

To install AWX, please view the Install guide.

To learn more about using AWX, and Tower, view the Tower docs site.

The AWX Project Frequently Asked Questions can be found here.

Contributing

  • Refer to the Contributing guide to get started developing, testing, and building AWX.
  • All code submissions are done through pull requests against the devel branch.
  • All contributors must use git commit --signoff for any commit to be merged, and agree that usage of --signoff constitutes agreement with the terms of DCO 1.1
  • 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, it's a good idea to join the #ansible-awx channel on irc.freenode.net, and talk about what you would like to do or add first. This not only helps everyone know what's going on, it also helps save time and effort, if the community decides some changes are needed.

Reporting Issues

If you're experiencing a problem, we encourage you to open an issue, and share your feedback. But before opening a new issue, we ask that you please take a look at our Issues guide.

Code of Conduct

We ask all of our community members and contributors to adhere to the Ansible code of conduct. If you have questions, or need assistance, please reach out to our community team at codeofconduct@ansible.com

Get Involved

We welcome your feedback and ideas. Here's how to reach us:

License

Apache v2