Standardise Best linux practice #46
Replies: 3 comments 1 reply
-
Let's open this with: Where to store config files ? :) From my technical perspective SignalK is a webserver(and more) I don't see it a user level app, it's a system service equals to nginx or mysql or pureftp. I don't see any usecase where It would make sense to run 2 instances on the same machine. Have you seen some? |
Beta Was this translation helpful? Give feedback.
-
I for one welcome setting the server properly in linux environments. The way things are now is more by accident than by any grand design. Very early on @mxtommy, the author of Kip webapp, coaxed us towards proper packaging, but that never gained momentum. No disagreement with the server being a daemon, not a user application. So where should everything be? This is what we are talking about (in addition to the server code in global node_modules)
|
Beta Was this translation helpful? Give feedback.
-
No worries! it is more than likely that this issue will be waiting for your contribution in 3 months time! Unless somebody else steps up to the plate... |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I would like to open a broad discussion about the best way to install/integrate SignalK on linux.
One of my objective it to standardize the way different projects integrate it to avoid work duplication and conflicting results.
The other objective is to determine best practices from OS point of view.
Beta Was this translation helpful? Give feedback.
All reactions