Documentation for logging doesn't specify where logs are stored #1025

lexander opened this Issue Mar 11, 2013 · 4 comments


None yet
3 participants

lexander commented Mar 11, 2013

Not very useful to have logging if you don't tell people where to view the log files.


rwaldura commented Mar 11, 2013

@lexander thanks for the report. Where should the log location be specified? Which section of the doc is it missing from?


lexander commented Mar 11, 2013

d'oh, I thought that the link to "Report an issue on this page" would include the location from which I came as a parameter.

Here's the page where I'd expect to find documentation on default log locations and how to configure those locations -


caridy commented Mar 21, 2013

@lexander mojito does not write logs into a file, that's not something the framework will do, but the underlaying infrastructure, in this case node.js. Mojito simply writes into the node.js console, whatever node.js does with the logs, dumping them into a file, or transmit them into an aggregated hub for multiple cores, or whatever other crazy idea people decide to implement has very little to do with mojito.

Aside from that, mojito is smart enough to detect if you're using TTY or not, to add colors into the logs or not, in case you boot the application using sparks or any other similar runner, and it works just fine with heroku and nodejitsu log aggregators.

caridy closed this Mar 21, 2013


lexander commented Mar 22, 2013

Ah, well then perhaps the documentation (this bug wasn't about what Mojito does or does-not do) should call that out. Here's a pull request with the change #1045

@jeffblack360 jeffblack360 pushed a commit to jeffblack360/mojito that referenced this issue Feb 7, 2014

@lexander lexander Updated docs to explain there are no log files
Used Caridy's explanation from yahoo#1025 (comment) to call out that there are no log files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment