{"id":3825,"date":"2016-04-19T12:08:09","date_gmt":"2016-04-19T12:08:09","guid":{"rendered":"http:\/\/www.garysieling.com\/blog\/?p=3825"},"modified":"2016-04-19T12:08:09","modified_gmt":"2016-04-19T12:08:09","slug":"node-log-files-forever","status":"publish","type":"post","link":"https:\/\/www.garysieling.com\/blog\/node-log-files-forever\/","title":{"rendered":"Node: log files with Forever"},"content":{"rendered":"

“Forever” has arguments to set log file output. It’s important to get the order of the arguments correct (your file goes at the end), because anything after the javascript file name is passed as arguments to your script.<\/p>\n

\nnode_modules\/forever\/bin\/forever start \\\n -l \/var\/log\/ssl-search-forever.log \\\n -o \/var\/log\/ssl-search-output.log \\\n -e \/var\/log\/ssl-search-error.log \\\n index.js\n<\/pre>\n
You can then watch the output of these, like so:<\/p>\n
\ntail -f \/var\/log\/ssl-search-*\n<\/pre>\n
You also probably want log rotation – this is what I’m using (will update later if I run into problems with it)<\/p>\n
\n\/var\/log\/ssl-search*.log {\n  daily\n  dateext\n  missingok\n  rotate 7\n  compress\n  delaycompress\n  notifempty\n  copytruncate\n}\n<\/pre>\n
If you want to control what goes into the access logs, you need to set up morgan correctly (this needs to happen at the beginning of the node app, not at the end):<\/p>\n
\napp.use(require(\"morgan\")(\"combined\"));\n<\/pre>\n","protected":false},"excerpt":{"rendered":"
Everything you need to use logging from a node app held together with the duct-tape known as forever<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[4],"tags":[345,387,388,389,559],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t