mention using several env vars for one setting in README

This commit is contained in:
Havoc Pennington 2011-11-28 01:37:29 -05:00
parent 789930cd8e
commit e6ee3d6232

View File

@ -208,8 +208,12 @@ vanishes if there's no value for `FORCED_BASEDIR`, but if you set
an environment variable `FORCED_BASEDIR` for example, it would be
used.
A natural extension of this idea is to support several different
environment variable names or system property names, if you aren't
sure which one will exist in the target environment.
Object fields and array elements with a `${?foo}` substitution
value just disappear if the substitution is not found.
value just disappear if the substitution is not found:
// this array could have one or two elements
path = [ "a", ${?OPTIONAL_A} ]