-
Notifications
You must be signed in to change notification settings - Fork 945
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
Feature request: Allow specifying a script to run when client exits via CLI #171
Comments
This is a neat idea! Thanks for the suggestion. |
We can also have -stop emailStopped.js so that it can email when the script has stopped. |
We would definitely accept a pull request for this - it's a great idea, but it will be a while before any of our team members have the time to devote to it. |
There is already an internal API for this. It seems that this would lend itself even better towards the From what I can tell of the bugs I've fixed tonight they come in mostly one flavor: options parsing hell Basically I'm pretty sure that forever has evolved to a point where people are probably passing 10+ options to the CLI everytime they run something.
|
Any update / workaround on this ? |
Duplicate of #437. |
I'd like to be able to do something like the following:
forever start -exit emailCrash.js app.js
Where the script emailCrash.js is called when forever detects that app.js is dead for good (that is, it's been revived the maximum number of times or is spinning).
The text was updated successfully, but these errors were encountered: