Closed bdf0506 closed 4 years ago
There's not much more to log on startup, but maybe what you're missing is -f
for follow, so you can see logging of actual requests between the 'stat and the browser.
That is, docker logs -f infinitude
-f
doesn't really do much in this case. When I look at the infitude source code, I see a bunch of lines like:
$c->app->log->debug("-------- Getting systems.xml (".$c->stash('id').") from infinitude.");
I would expect that starting the container with a mode of debug, it would actually print these debug log messages, but this doesn't seem to be the case. I seem to recall that when I was running infinitude not in a docker container, there was either a log file created, or it was written to stdout or something similar.
Ah, figured it out. To get debug logs, you don't want a MODE of "debug", but rather you want a MODE of "development". Doing this will then print debug messages to docker logs.
MODE is set to development
Can't find serial device: /dev/ttyUSB0. Serial monitoring disabled.
[Tue Jun 23 15:49:36 2020] [info] Listening at "http://*:3000"
[Tue Jun 23 15:49:40 2020] [debug] GET "/"
[Tue Jun 23 15:49:40 2020] [debug] Routing to a callback
[Tue Jun 23 15:49:40 2020] [debug] 304 Not Modified (0.000723s, 1383.126/s)
[Tue Jun 23 15:49:40 2020] [debug] GET "/serial"
[Tue Jun 23 15:49:40 2020] [debug] Routing to a callback
Overall, I believe that some changes should be made to the Infinitude code, so that some messages are INFO rather than DEBUG, but will leave that to @nebulous to make that call.
Ah, nice. Sorry I haven't had a chance to dig into my dev system for this, but I'm glad to see you got it sorted. Any debugging levels currently are completely arbitrary thusfar, so I'll be happy to merge a PR with level changes!
Maybe I am missing something basic, but how can I see debug logs via docker?
Even when I set mode to Debug, i would expect to see a little more than this: