-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I like this. But I have a question. #1
Comments
+1 I got so excited when I first found this module - only shortly to be let down finding out that in order for it to work the user had to login. Big let down. This could be a huge module for users forced to deploy node on windows too! |
+1 Did anyone solve this? |
Nope - Forever is working for me in production. If the PM2 folks ever get around to fixing this, I may switch back, the forever solution is working for me with no headaches or work arounds |
This is indeed an issue. I opened #2 to solve this. |
Just FYI, for now I solved it using Autologon https://technet.microsoft.com/en-us/sysinternals/bb963905 |
I like this. Thank you. But I have a question.
When I did pm2 save and windows server restarted , pm2 not started before login.
How can i solve this problem?
I added this(wscript.exe "C:\Users\youngsoonl\AppData\Roaming\npm\node_modules\pm2-windows-startup\invisible.vbs" "C:\Users\youngsoonl\AppData\Roaming\npm\node_modules\pm2-windows-startup\pm2_resurrect.cmd") to registry into LOCAL_MACHINE , But It was not working when server restart automatically before login.
The text was updated successfully, but these errors were encountered: