-
Notifications
You must be signed in to change notification settings - Fork 946
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
Seems broken in node v0.4.0 #26
Comments
Thanks. Are you installing from npm@latest or are you cloning the repository and trying it? I was noticing some issues with daemon.node (one of the libraries I maintain that forever depends on) in nodejs 0.4.0. I will investigate today / tomorrow and get back to you. |
I installed it on a fresh machine via |
Hmm... try this: npm install daemon@0.2.0 cd /path/to/src git clone git@github.com:indexzero/forever.git cd forever npm install . Let me know if that's any different for you. The above script will install daemon.node 0.2.0 and forever@HEAD. Sometimes it's useful to check the logs so before you run forever try this: forever cleanlogs forever start myapp.js ls /tmp/forever # Send me the dump of these log files |
Will try installing daemon and forever from source later. I took a look in the logfile after cleaning the logs and starting again. It's completely empty. |
Allright, I followed your steps. When I start forever I get this now:
|
Pushed daemon.node |
Works like a charm, awesome! |
Tested in on Mac OSX Snow Leopard and Ubuntu Maverick
If I am running on node v0.4.0 and I say
nothing gets started, so if I run
I get
The text was updated successfully, but these errors were encountered: