You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 28, 2022. It is now read-only.
Currently we are logging status and error messages to the Standard input/output. This would not cater for a message queue hosted on a server that is not under 24/7 human supervision.
Justification
simplemq is meant to be run on servers. This entails that logs of errors, warnings and the like are saved on files. Such files can be checked later in case an error occurs.
Notes
Winston seems to be a very popular option. One needs to look into how to structure it to log to stdin during development and to logfiles mostly when in production.
The text was updated successfully, but these errors were encountered:
Problem Statement
Currently we are logging status and error messages to the Standard input/output. This would not cater for a message queue hosted on a server that is not under 24/7 human supervision.
Justification
simplemq is meant to be run on servers. This entails that logs of errors, warnings and the like are saved on files. Such files can be checked later in case an error occurs.
Notes
Winston seems to be a very popular option. One needs to look into how to structure it to log to stdin during development and to logfiles mostly when in production.
The text was updated successfully, but these errors were encountered: