-
-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update raspberry_pi_installation.md #1820
base: master
Are you sure you want to change the base?
Conversation
added cautionary notes about nodejs versions
NOTE: IMPORTANT - installing a higher version of nodejs (eg V20) is known to cause issues with a number of plugins and CAN adaptors. | ||
Note: Some applications that are installed after signalk-server are known to "auto" install updated/most recent version of nodejs... | ||
which as above breaks things .... take care to avoid this! | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I think there are multiple issues in this addition:
- The previous step calls for installing NodeJS (note the capitalization) 18 and this about "higher version" and refers to V20. To me this is needlessly confusing
- Why is there one NOTE and and another note?
- I am not aware of other applications updating nodejs version - can you be more specific? And how would an end user take care to avoid thid?
This document is about installing signalk-server on a system that has no NodeJS or a previous installation, but the notes are about updating Node. Maybe we could find some other place where these notes would have a more appropriate home, like https://github.com/SignalK/signalk-server/wiki/Installing-and-Updating-Node.js ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i did follow the instructions as presented, all good.
however when installing either influx or grafana - i believe it was the latter,
the install script - went ahead and update nodejs… (to V20) … this created two days of fault finding and unnecessary debugging with help from other signalk users.
FAQs would at best be looked at after a user encounters an issue … i was thinking “how” to make sure that as part of the install process .. that a user be alerted to beware of this …
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i did add the following into the FAQ
this ok?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neither Influx nor Grafana are NodeJS based, I sincerely doubt they caused a NodeJS update.¨
Also the problem is not really NodeJS v20, instead any update of a major NodeJS version may break things and in practise requires a reinstall of the server and the plugins.
all noted, are my additions to the FAQs ok? |
added cautionary notes about nodejs versions