From a7d07e44b7a11e70b1a5d294aa6714f1a505046c Mon Sep 17 00:00:00 2001
From: Lloyd Hilaiel <lloyd@hilaiel.com>
Date: Thu, 18 Aug 2011 13:31:22 +0300
Subject: [PATCH] interface winston logging better, use the Console transport
when running in the dev harness rather than manually logging to console (yay
for colorized output)
---
libs/logging.js | 3 +++
run.js | 4 +---
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/libs/logging.js b/libs/logging.js
index deb0aa174..b167c6eb0 100644
--- a/libs/logging.js
+++ b/libs/logging.js
@@ -76,3 +76,6 @@ exports.logger = new (winston.Logger)({
exports.logger.emitErrs = false;
+exports.enableConsoleLogging = function() {
+ exports.logger.add(winston.transports.Console, { colorize: true });
+};
\ No newline at end of file
diff --git a/run.js b/run.js
index 3290f0705..fd1c0c38b 100755
--- a/run.js
+++ b/run.js
@@ -46,9 +46,7 @@ var sys = require("sys"),
substitution = require('./libs/substitute.js');
// when running under the harness, let's also output log messages to the terminal
-require('./libs/logging.js').logger.on('log', function(transport, level, msg, meta) {
- console.log(level + ":", msg);
-});
+require('./libs/logging.js').enableConsoleLogging();
var configuration = require('./libs/configuration.js');
--
GitLab