Conversation
|
Hey, thanks for the contribution. What's your use case for this? Also, since this is a boolean flag and true by default, it'd be better to call the flag |
The motivation is that I use miniserve a lot in scripts/makefiles where the port is set explicitly and doesn't change. For these use cases, miniserve is used as a local server that will only be accessed via localhost and so I don't need (nor want) to see any of the other interfaces the server is available on. An alternative would be to pipe the output of miniserve to /dev/null, but it is nice to see some of the output such as the version, port, and path. Also, since this is a boolean flag and true by default, it'd be better to call the flag Happy to make the change 😄 |
|
Alright, in that case, what do you think about a |
|
SGTM 👍 I'll update the PR |
|
@svenstaro updated the commit and PR 😄 |
This change adds the
--quietflag (along with theMINISERVE_QUIETenv variable) which, when enabled, reduce output and silences warnings.For example