Quote:
Originally Posted by conachair
search came up with no .signalk folder on the drive.
|
Seeing the comment above from teppokurki, out of curiosity, have you tried actually to launch the signalk-server? It looks like the .signalk directory will be create at the launch. My remark was if one already has such a folder.
BTW, I can see from the thread Rick linked here that you have been using versions of node.js like 13, 10 etc. In this domain of signalk-server, and with other npm services like TiddlyWiki (for authoring) I am using always the long term support version, which seems to be currently 12.13.1 LTS. Unless you have some development
work going on, I would suggest you to remove
and manually clean all the traces of the other installations, then start again, from a clean table using a node.js LTS version.
Please report here your findings, they will be very much appreciated for the
documentation. And, as teppokurki said, he and other developers of this great
software which signalk-server without doubt is, would also appreciate to be kept informed here:
https://github.com/SignalK/signalk-server-node/issues