From 7ba063c6bb28310d3faf15d19ba7774b06b311de Mon Sep 17 00:00:00 2001
From: Edgars Beigarts <edgars.beigarts@gmail.com>
Date: Wed, 15 Mar 2017 14:52:29 +0200
Subject: [PATCH] Enable nginx and docker on system startup when using
 bootstrap.sh on CentOS

---
 bootstrap.sh                        |  4 ++++
 docs/getting-started/install/rpm.md | 11 ++++++++---
 2 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/bootstrap.sh b/bootstrap.sh
index b787f47d0..087a4d424 100755
--- a/bootstrap.sh
+++ b/bootstrap.sh
@@ -167,6 +167,10 @@ install-dokku-from-rpm-package() {
     yum -y install herokuish dokku
   fi
 
+  echo "--> Enabling docker and nginx on system startup"
+  systemctl enable docker
+  systemctl enable nginx
+
   echo "--> Starting nginx"
   systemctl start nginx
 }
diff --git a/docs/getting-started/install/rpm.md b/docs/getting-started/install/rpm.md
index f51e9283f..8087c6b26 100644
--- a/docs/getting-started/install/rpm.md
+++ b/docs/getting-started/install/rpm.md
@@ -7,16 +7,21 @@
 Dokku defaults to being installed via RPM package on CentOS 7. While certain hosts may require extra work to get running, you may optionally wish to automate the installation of Dokku without the use of our `bootstrap.sh` bash script. The following are the steps run by said script:
 
 ```shell
-# install docker
+# Install docker
 curl -fsSL https://get.docker.com/ | sh
 
-# install epel for nginx packages to be available
+# Install epel for nginx packages to be available
 sudo yum install -y epel-release
 
-# install dokku
+# Install dokku
 curl -s https://packagecloud.io/install/repositories/dokku/dokku/script.rpm.sh | sudo bash
 sudo yum install -y herokuish dokku
 sudo dokku plugin:install-dependencies --core
+systemctl start nginx
+
+# Enable docker and nginx on system startup
+systemctl enable docker
+systemctl enable nginx
 ```
 
 The [devicemapper](https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/) is the default Docker storage driver on CentOS 7 and defaults to a configuration mode known as `loop-lvm`. This mode is designed to work out-of-the-box with no additional configuration. However, production deployments should not run under `loop-lvm` mode. The preferred configuration for production deployments is [`direct-lvm`](https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/#/configure-direct-lvm-mode-for-production).