Project

General

Profile

Actions
Copy link

action #1638

closed

Proper management of log files for deployment

Added by ancorgs almost 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
lnussel
Category:
-
Target version:
Sprint 03
Start date:
2014-02-20
Due date:
% Done:

100%

Estimated time:
3.00 h

Description

Right now, the application logs to $APPDIR/log/$MODE.log if the log directory is there. If it's not there, the app logs to STDOUT. For proper deployment it should log to /var/log or, at least, do something better than the current default.

Actions
Copy link
 #1

Updated by ancorgs almost 11 years ago

  • Priority changed from Urgent to Immediate
Actions
Copy link
 #2

Updated by ancorgs almost 11 years ago

  • Target version set to Sprint 03
Actions
Copy link
 #3

Updated by ancorgs almost 11 years ago

  • Assignee set to lnussel
Actions
Copy link
 #4

Updated by lnussel almost 11 years ago

  • Status changed from New to In Progress

I've added configuration options for the log file and log level to the configuration file. By default both are empty which means mojo logs to stderr. With systemd that is fine as it catches the output on stderr and writes it to the journal.
It would probably be interesting to log the requests somewhere else separately.

Actions
Copy link
 #5

Updated by lnussel almost 11 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF