<p>Summary: beego app served by supervisord deployed behind nginx reverse proxy on linux.</p>
<p>When the app is running locally (via <strong>bee run</strong>), I have all the route logging (timestamp, http method, match/notmatch, etc). When the app is compiled and deployed to run on the external server, all that logging is gone.</p>
<p>Went deep diving into <em>beego</em> code and found that in <strong>beego/logs/log.go</strong> approx. line #192 (range bl.outputs) that <em>bl.outputs</em> is empty (but only when compiled - via go build).</p>
<p>Anybody have any thoughts? I'm unable to see why/when <em>bl.outputs</em> gets populated/emptied.</p>
