<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>
这是一个分享于 的资源,其中的信息可能已经有所发展或是发生改变。
入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889
- 请尽量让自己的回复能够对别人有帮助
- 支持 Markdown 格式, **粗体**、~~删除线~~、
`单行代码`
- 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
- 图片支持拖拽、截图粘贴等方式上传