Windows support about pm2 HOT 13 CLOSED

Hello, thanks for reporting issues.

PM2 is a production module, who should be mainly used on Linux servers. I haven't tried it on other platforms than Linux.

Feel free to contribute if you want to integrate this compatibility feature !

Thanks

from pm2.

When changed detached: true to false in Satan.launchDaemon daemon forking options got this error:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn Unknown system errno 203
    at errnoException (child_process.js:945:11)
    at Process.ChildProcess._handle.onexit (child_process.js:736:34)

but cant find what is that 203 error.

from pm2.

how about use nssm in windows? there is another project: http://jfromaniello.github.io/winser/

from pm2.

I was trying to get pm2 to work on my Windows-based development workstation for testing purposes, but whenever I invoke it with any parameters, I get:

events.js:71
        throw arguments[1]; // Unhandled 'error' event
                       ^
Error: connect EADDRNOTAVAIL
    at errnoException (net.js:770:11)
    at Object.afterConnect [as oncomplete] (net.js:761:19)

I tried debugging pm2, but I really didn't get anywhere. What is the execution path after everything in the pm2 file is defined?

from pm2.

We just launched a crowd funding campaign on boutysource for the Windows support:

https://www.bountysource.com/teams/keymetricsio/fundraisers/600-pm2-windows-support

Hope we will get enough attention for this Windows feature !

from pm2.

Could you try the Windows support:

C:/ $ npm install git://github.com/Unitech/pm2#development -g

Give us your feedback!

from pm2.

@Unitech Well, it starts our application. Which is more than what I got on the first try with pm2 on Windows ;)

from pm2.

Good (: Apparently I got a feedback about the PID that is not refreshed on restart ( #777 ) Do you have the same bug?

Thanks

from pm2.

I'll have to properly test at work during the week and I really have to get more into the specifics of pm2. I'll post if I trip over anything.

from pm2.

@oliversalzburg Thanks! Windows tester are not easy to find these days! (don't ask why...)

from pm2.

I have the same problem on widows server.

from pm2.

I also still have this problem, also after installing the development branch

from pm2.

Try setting PM2_HOME to your C:\Users.pm2 directory (Win Vista/7/8)
Or take a simple one line patch described in this pull: #982

from pm2.