From cf0b58152b855f3fa16ea675b1ce3fc71c995444 Mon Sep 17 00:00:00 2001 From: Scott Koranda Date: Thu, 25 May 2017 15:47:42 -0500 Subject: [PATCH] better table of contents --- docs/advanced-configuration.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/docs/advanced-configuration.md b/docs/advanced-configuration.md index ea80646..209c833 100644 --- a/docs/advanced-configuration.md +++ b/docs/advanced-configuration.md @@ -26,12 +26,11 @@ The services deployed in containers instantiated using images built from this re configured in a number of different ways. ##### Table of Contents -[Environment Variables](#environ) -[Secrets](#secrets) -[Full Control](#full) +* [Environment Variables](#environ) +* [Secrets](#secrets) +* [Full Control](#full) - -## Environment Variables +## Environment Variables Most deployment details may be set using environment variables set for the container. The entrypoint scripts will attempt to use values from environment variables and if not @@ -83,8 +82,7 @@ Coming soon... ### OpenLDAP slapd Coming soon... - -## Secrets +## Secrets Some deployers prefer not to use environment variables to inject secrets to avoid having secrets in YAML files saved for example in a code repository. @@ -239,8 +237,7 @@ If no files are configured the container uses a default self-signed certificate Coming soon... - -## Full control +## Full control Deployers needing full control may inject configuration and deployment details directly. The entrypoint scripts will *not* overwrite any details found so directly injected