programmatic examples

[sandro-pasquali]

Are there any programmatic examples that go into more depth? Specifically, how do I pass arguments to the target script -- i've tried nodeArgs, scriptArgs, env, node_args, script_args -- and i don't see those values anywhere in the process.

Great tool, looking forward to using it.

[soyuka]

Is this what you're looking for ?

[sandro-pasquali]

I looked at that. It seems to indicate that the second argument to #start is a map of options, and that (I think) these are the options for passing arguments to the script: nodeArgs(arr), scriptArgs(arr)... yet, when I set those pm2.start('somescript.js', { name: 'test', scriptArgs : ['foo', 'bar'] } ...) I'm not catching them via process.argv in the target script.

I'm assuming it is modeled like the second argument to child_process.fork('script', [args]). It doesn't seem to be.

Thanks for the help. I fear i'm missing something obvious.

[soyuka]

I'm using pm2.startJson which allows you to pass everything from a json declaration.

When you're using pm2.start you're basically calling this function, nodeArgs are the arguments to pass to node instance, scriptArgs should be your script arguments.

I'm also seeing rawArgs (l57), those are usually called from the command line: pm2 start myApp.js -- var=test - process.argv will have a property var with value test.

[sandro-pasquali]

Thanks. After playing around with both solutions and reading the code closely I've achieved what I wanted to achieve.

As the child (fork) process should have a communication channel (as per the node spec for #fork), I was wondering as well how to access that? To achieve something like the follow, where the forked process can send a message to its master:

pm2.start(...,...,function(err, proc) {
  proc.on('message', function(msg) { ... }
})

[joshgummersall]

@sandro-pasquali any chance you could elaborate on the solution you came up with?