From 49cf31baadb38e271c2ed77354cefa2063259c31 Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Fri, 18 Mar 2016 10:42:02 -0400 Subject: [PATCH] Document when configuration variables are available. Closes #1860 [ci skip] --- docs/configuration-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration-management.md b/docs/configuration-management.md index 8eee63c7e..7fbceacf7 100644 --- a/docs/configuration-management.md +++ b/docs/configuration-management.md @@ -11,7 +11,7 @@ config:set (|--global) KEY1=VALUE1 [KEY2=VALUE2 ...] Set one or more config config:unset (|--global) KEY1 [KEY2 ...] Unset one or more config vars ``` -The variables are available both at run time and during the application build/compilation step. +The variables are available both at run time and during the application build/compilation step for buildpack-based deploys. For security reasons - and as per [docker recommendations](https://github.com/docker/docker/issues/13490) - Dockerfile-based deploys have variables available *only* during runtime, as noted in [this issue](https://github.com/dokku/dokku/issues/1860). > Note: Global `ENV` files are sourced before app-specific `ENV` files. This means that app-specific variables will take precedence over global variables. Configuring your global `ENV` file is manual, and should be considered potentially dangerous as configuration applies to all applications.