Open emilecantin opened 6 years ago
Teppo Kurki on 2016-8-4 15:26:21: Great writeup!
This should help people who have struggled with getting Signal K server running automatically after boot. Same stuff applies to node and java servers.
You can actually skip the start-signalk.sh file (which btw is not included in your post) by setting up the environment variable SIGNALK_NODE_SETTINGS to point to your own settings file and starting the bin/signalk-server directly from systemd.
Another nice trick is to have systemd set up the socket that the server uses. This way you can have Signal K Node Server running on port 80 and don't need to have the port explicitly in your urls.
For an example see
https://github.com/tkurki/m...
and
https://github.com/tkurki/m...
Comment imported from Disqus
emilecantin on 2016-8-4 15:41:14: Thanks! I've updated the post to include the file I missed. As for port 80, I was planning to simply use an nginx reverse proxy and serve static files with that, but I haven't decided yet. Comment imported from Disqus
This issue is a container for comments on this post.