don't log warning if env file doesn't exist

strongloop / node-foreman

A Node.js Version of Foreman

http://strongloop.github.io/node-foreman/

Other

1.27k stars 119 forks source link

don't log warning if env file doesn't exist #115

Closed rmg closed 6 years ago

rmg commented 8 years ago

Rather than adding CLI flags and introducing log levels, this seems like the simplest way to address #95.

rmg commented 8 years ago

@dickeyxxx do you have any objections to this change in behaviour?

aseemk commented 8 years ago

Sorry for the delay, @rmg, but this seems great to me! Thank you for knocking out. =)

mediafreakch commented 8 years ago

One argument for a more advanced solution might be that if I run nf to pipe something somewhere to be re-used by another program. Imagine this: nf run browserify index.js > build.js.

build.js currently would throw an exception because foreman prints status messages into it...

This currently requires me to add another .env handling package on top of foreman...

jdx commented 8 years ago

yeah I don't see any need to have this warning