Here is a PR that adds support for a stop message (msg.stop) which will kill suspend restarting the process. it also makes the msg.start message trigger a restart as per existing docs.
first contribution so please feel free to give guidance on whatever ..
also i did not see any existing unit tests so no additional ones supplied yet.
in the node - if you deselect the relaunch option then msg.kill will stop the process and it won't automatically restart, and will wait for a msg.start. Likewise if you deselect the autostart it won't start on deploy and will wait for a msg.start message.
So I'm still not seeing what extra capability this is adding yet...
@dceejay Slightly off topic but, I was using the node-red-node-daemon node today and had a look through the code and saw that it may support a msg.cr property as a boolean. I'm I correct in assuming that the property can be used to "Add [enter] to a message sent"? I couldn't find anything about it in the nodes help documentation and solved my issue without it anyway but would be nice to clarify for future projects.
i can find any link to node-red-contrib-daemon .. but the standard one - node-red-node-daemon has that feature supported in the ui.. and it is maintained as node.cr in the code..
No - the node does not support use of msg.cr - It is a property of the node (node.cr) - that is set at edit time whether to add a cr to each line sent or not. It's can't be changed during runtime via a message.