-
Notifications
You must be signed in to change notification settings - Fork 13
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
rhizome with forever? #129
Comments
hey! Sorry for slow answer. I also use forever, and I usually call the whole path for example |
I can't quite get it to work. but this: throws
Any idea why? That's obviously the correct path because it starts rhizome, but just doesn't work with forever in front of it. thanks again. |
aah sorry my mistake. Here is probably what you should run |
Hmm can you think of any reason why this wouldn't be working: It runs forever but doesn't start rhizome. |
Hmm no ... not really. What error message do you get? |
Unfortunately there is no error. Forever says it's started but it just doesn't start rhizome. This is what happens:
|
then you have some other bug ... activate logging to see it :
and check out what's in the log with :
|
I'd like to use forever to run rhizome on EC2 so I don't have to use the terminal to start it before a performance, so there's less things to worry about. Forever runs your script using
forever start app.js
so I can't figure out how to get it to userhizome config.js
.forever rhizome config.js
doesn't work. Have you ever used this? Maybe there's a way I can change the way rhizome is called back to start in order to use forever?thanks again.
The text was updated successfully, but these errors were encountered: