[Pkg-javascript-commits] [node-log-driver] 05/49: Update README.md
Bastien Roucariès
rouca at moszumanska.debian.org
Thu Feb 22 12:56:58 UTC 2018
This is an automated email from the git hooks/post-receive script.
rouca pushed a commit to branch master
in repository node-log-driver.
commit c4a90b72e4744cf8d1350398e59b50b746d989d3
Author: Gregg Caines <gregg at caines.ca>
Date: Sun Mar 17 20:17:49 2013 -0700
Update README.md
---
README.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/README.md b/README.md
index 84fc7b6..255e561 100644
--- a/README.md
+++ b/README.md
@@ -8,15 +8,19 @@ Logdriver is a node.js logger that only logs to stdout.
##There are some other nice advantages:
* When working on your app locally, logs just show up in stdout just like if you'd used console.log(). That's a heck of a lot simpler than tailing a log file.
* Logging transports can be externalized from your app entirely, and completely decoupled. This means if you want to log to irc, you write an irc client script that reads from stdin, and you just pipe your app's output to that script.
+
```console
node yourapp.js 2>&1 | node ircloggerbot.js
```
* You can still easily log to a file on a production server by piping your stdout and stderr to a file like so when you initialize your app:
+
```console
node yourapp.js 2>&1 >> somefile.log
```
+
NB: If you're logging to a file, [Logrotate](http://linuxcommand.org/man_pages/logrotate8.html) is probably going to be your best friend.
* You can still easily log to syslog by piping your stdout and stderr to the 'logger' command like so:
+
```console
node yourapp.js 2>&1 | logger
```
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-javascript/node-log-driver.git
More information about the Pkg-javascript-commits
mailing list