summaryrefslogtreecommitdiffstats
path: root/INSTALL.md
diff options
context:
space:
mode:
authorElijah DeLee <kdelee@gmail.com>2019-03-27 16:52:42 +0100
committerElijah DeLee <kdelee@gmail.com>2019-03-27 16:54:33 +0100
commit7dd635cd8da40339b59812c5dbb5cc831494d99d (patch)
treef62de9eb918757f92b1d57d3ba7385377687fea8 /INSTALL.md
parentMerge pull request #3515 from shanemcd/docker-compose-permissions (diff)
downloadawx-7dd635cd8da40339b59812c5dbb5cc831494d99d.tar.xz
awx-7dd635cd8da40339b59812c5dbb5cc831494d99d.zip
update install docs
Diffstat (limited to 'INSTALL.md')
-rw-r--r--INSTALL.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/INSTALL.md b/INSTALL.md
index 58f9fa87c0..bf0021472f 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -73,7 +73,7 @@ The system that runs the AWX service will need to satisfy the following requirem
- At least 2 cpu cores
- At least 20GB of space
- Running Docker, Openshift, or Kubernetes
-- If you choose to use an external PostgreSQL database, please note that the minimum version is 9.4.
+- If you choose to use an external PostgreSQL database, please note that the minimum version is 9.6+.
### AWX Tunables
@@ -81,7 +81,7 @@ The system that runs the AWX service will need to satisfy the following requirem
### Choose a deployment platform
-We currently support running AWX as a containerized application using Docker images deployed to either an OpenShift cluster, docker-compose or a standalone Docker daemon. The remainder of this document will walk you through the process of building the images, and deploying them to either platform.
+We currently support running AWX as a containerized application using Docker images deployed to either an OpenShift cluster or docker-compose. The remainder of this document will walk you through the process of building the images, and deploying them to either platform.
The [installer](./installer) directory contains an [inventory](./installer/inventory) file, and a playbook, [install.yml](./installer/install.yml). You'll begin by setting variables in the inventory file according to the platform you wish to use, and then you'll start the image build and deployment process by running the playbook.