You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I want to deploy my node.js app in an isolated environment and nar fits perfectly so far. I have a question though about some of the behaviour when you start the binary-like package e.g. ./myapp-0.1.0-linux-x64.nar then it runs the start command in the package.json which is nice, but my question now how does it work with the process stying in the foreground/backgroun (daeomonizing non deamonizing mode)? I want to manage that binary with supervisor (http://supervisord.org/) but now running into issues because I start the binary directly which then seems to spawn the node process(es) but then supervisor doesn't know about those and has issues killing them amongst others.
I am still testing a few different ways and getting close to having something that works but I was just curios how it works within nar. If you could shed some light around that topic that would be much appreciated.
The text was updated successfully, but these errors were encountered:
Hi, I want to deploy my node.js app in an isolated environment and nar fits perfectly so far. I have a question though about some of the behaviour when you start the binary-like package e.g.
./myapp-0.1.0-linux-x64.nar
then it runs thestart
command in the package.json which is nice, but my question now how does it work with the process stying in the foreground/backgroun (daeomonizing non deamonizing mode)? I want to manage that binary with supervisor (http://supervisord.org/) but now running into issues because I start the binary directly which then seems to spawn the node process(es) but then supervisor doesn't know about those and has issues killing them amongst others.I am still testing a few different ways and getting close to having something that works but I was just curios how it works within nar. If you could shed some light around that topic that would be much appreciated.
The text was updated successfully, but these errors were encountered: