Running an upgrade should also append its output to logs

[psychobunny]

When running ./nodebb upgrade, the output should also append to logs/output.log just as it does for ./nodebb start. These logs can be viewed by running ./nodebb log.

Good for beginners, feel free to ask here for tips on getting started.

[pitaj]

@Saksham-1612 Hi! We're always open to contributions. Let me know if you have any questions.

[neha-gunta]

Is the issue still open?

[julianlam]

If you can fix it, open a pull request 👌

[neha-gunta]

By output, do we mean the console.log output? If yes, So is the task about logging them using the winston logger?
If no, can you please elaborate on the output part. TIA!

[julianlam]

@neha-gunta thanks for the follow up. Currently both the upgrade and regular running of NodeBB call setupWinston, and all it does is output to the console.

The issue is a little complicated because our current Winston config does not have any settings for file output. If you want to resolve this issue, you would have to fix that config so it outputs to the proper file location for both regular running of NodeBB, and for upgrade scripts... Basically anywhere that calls setupWinston

[julianlam]

There is existing logic that takes stdout and stderr and redirects them to output.log. you would probably want to remove that in favor of the Winston configuration.