Closed katlimruiz closed 5 years ago
Did you install with the -g
flag?
$ npm install --production -g pino-papertrail
Then you should be able to call pino-papertrail
from a terminal and not get the error.
well RUN npm link pino-papertrail
also worked, but your solution is better.
It seems "weird" first to add one more package at deploy time, but I guess it makes sense since you want to decide where to log up until the last step, and also leave it open to select another one later if needed.
Do you need to do an
npm link pino-papertrail
so it can be called after the pipe?If so, how would you do this in a docker container?