Ryan Petrello 2ba9e56033 Include the Tower venv in the isolated bubblewrapped arguments.
This moves the container-based code location and venvs.
The goal here is that the paths of Tower source for isolated
vs normal nodes matches (both in prod and local development) so that we
don't have to add a bunch of additional bwrap argument logic for
<location-of-isolated-tower-venv>.
2017-06-19 15:52:54 -04:00
2017-06-16 16:38:14 -04:00
2016-02-01 18:37:56 -05:00
2017-06-12 09:53:11 -04:00
2015-02-06 09:47:41 -05:00
2016-07-22 13:19:57 -04:00
2016-12-20 15:34:29 -05:00
2017-06-12 09:53:11 -04:00
2016-03-04 16:19:00 -05:00
2015-06-11 16:10:23 -04:00
2016-11-11 16:01:45 -05:00
2016-11-15 17:31:21 -05:00

Build Status Requirements Status

Ansible Tower

Tower provides a web-based user interface, REST API and task engine built on top of Ansible.

Resources

Refer to CONTRIBUTING.md to get started developing, testing and building Tower.

Refer to setup/README.md to get started deploying Tower.

Refer to docs/build_system.md for more about Jenkins and installing nightly builds (as opposed to running from source).

Refer to docs/release_process.md for information on the steps involved in creating a release.

Refer to http://docs.ansible.com/ansible-tower/index.html for information on installing/upgrading, setup, troubleshooting, and much more.

Description
AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
Readme 428 MiB
Languages
Python 97.8%
Jinja 0.9%
Makefile 0.5%
Shell 0.3%
HTML 0.2%
Other 0.2%