File tree Expand file tree Collapse file tree 1 file changed +9
-0
lines changed Expand file tree Collapse file tree 1 file changed +9
-0
lines changed Original file line number Diff line number Diff line change @@ -420,6 +420,9 @@ read immediately whenever parsing the configuration file, so if it changes
420420afterwards it requires a configuration reload to see the changes. This
421421functionality is especially useful for reading SSL certificates and keys.
422422
423+ If you use ` %{variables} ` in file names, these will be expanded by target
424+ process and not config process, which can cause problems with permissions.
425+
423426## Variable Expansion
424427
425428It's possible to refer to other earlier settings as ` $SET:name ` .
@@ -436,6 +439,8 @@ However, you must be careful with the ordering of these in the configuration
436439file, because the ` $SET:variables ` are expanded immediately while parsing the
437440config file and they're not updated later.
438441
442+ See also [[ link,settings_variables]] .
443+
439444## Environment Variables
440445
441446It is possible use ` $ENV:name ` to expand values from environment.
@@ -447,3 +452,7 @@ Note that these are also Case Sensitive.
447452
448453These can also be used for external config files, but you need to list them in
449454[[ setting,import_environment]] so that processes can see them.
455+
456+ If you use ` ${env:} ` instead of ` $ENV ` , this will cause the environment variable(s) to be
457+ evaluated later. This can cause problems with files since config process cannot open
458+ them anymore. It is recommended to use ` $ENV ` instead when possible.
You can’t perform that action at this time.
0 commit comments