environment.yaml - Including non-existing variable throws an error

mottosso / be

minimal directory and environment management system for collaborative creative projects

GNU Lesser General Public License v2.1

47 stars 4 forks source link

Closed mottosso closed 9 years ago

mottosso commented 9 years ago

When setting up an environment key and referencing an unavailable variable, be refuses to start.

For example.

**be.yaml

environment:
- MYPATHS: ["$DOES_NOT_EXIST", "c:\otherpath"]

What should have happened is for the missing key to simply not get added.