Oh! I missed out on "debug.log" as well. Could it be wrong file permissions? There's a lot that can go wrong when running from "cron".
I normally add "1>/tmp/cron-app-tmp.log 2>&1" when I can't figure out what is going on. On Wednesday, March 23, 2016 at 3:07:20 PM UTC+1, Jan Henning Thorsen wrote: > > Have you tried "perl /home/lab/MyApp get -m production > /update?filter=opened" ? > > For more information: mojo get --help > > > > On Wednesday, March 23, 2016 at 12:09:37 PM UTC+1, Pavel Serikov wrote: >> >> I'm calling one of route of my Mojolicious::Lite app via cron, using >> command-line >> interface <https://metacpan.org/pod/Mojolicious::Commands>, like this: >> >> */5 * * * * perl /home/lab/MyApp get /update?filter=opened >> >> inside MyApp there is some logging strings like >> >> app->log->info('Variable a:'.$a); >> >> But as I noticed that app is not writing to production.log or debug.log >> when accessed via command line. >> >> How to call same (as access to routes via browser) logging when access >> the app via command line? >> > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
