<div dir="ltr">Hi,<div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 27, 2013 at 12:50 AM, David Golden <span dir="ltr"><<a href="mailto:xdg@xdg.me" target="_blank">xdg@xdg.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm looking at logging and notice that there don't appear to be any<br>
handlers other than the core ones.<br>
<br>
Then I look at Dancer2::Logger::File and see these issues:<br>
<br>
* log_path is documented but no code actually uses it<br>
<br>
* holds an open file-handle. No flush/reopen on a signal, so log<br>
rotation means restarting the whole app<br>
<br>
So what are people using Dancer2 actually doing for logging? Just<br>
Console grabbed by a supervisor daemon?<br></blockquote><div><br></div><div style>Deployed two apps on Dancer2 to production last week, and went through the same process. Due to time constraints I ended up logging to console and used multilog to handle log rotation.</div>
<div style><br></div><div style>So yes, Console grabbed by a superviser daemon.</div><div style><br></div><div style>Bye,</div></div>-- <br>Pedro Melo<br>@pedromelo<br><a href="http://www.simplicidade.org/" target="_blank">http://www.simplicidade.org/</a><br>
<a href="mailto:xmpp%3Amelo@simplicidade.org" target="_blank">xmpp:melo@simplicidade.org</a><br>mailto:<a href="mailto:melo@simplicidade.org" target="_blank">melo@simplicidade.org</a>
</div></div>