Scripts started within node with different options replaces existing script process about forever

[indexzero]

This was an interesting bug to fix. Fixed in 1c16e81

Basically, the *.fvr and *.pid files that forever was storing were based on the process.pid of the current running process. So starting two processes caused the second process to overwrite the files for the first proces. Forever files are now keys off a uid that can be passed in or is automatically generated when creating instances of forever.Monitor (aka forever.Forever): https://github.com/indexzero/forever/blob/v0.5.x/lib/forever/monitor.js#L32

[marklubi]

Thank you very much for getting the issue tracked down. The fix is extremely helpful! We spin up a whole slew of node apps (same app across various ports) and by being able to spin them up from a bootstrapping node instance were were able to save on a lot of memory usage.