-
Notifications
You must be signed in to change notification settings - Fork 944
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
Future Forever #1094
Comments
@Alexander1414x Forever is no longer under active development and full relies on the community for new features. Would you be open to submit a PR? |
@kibertoad this is actually news to me, is there info on this anywhere? What is the alternative people are using these days? Thanks! |
@framerate Yes. Literally the first paragraph in the readme :). For modern dockerized production environments you are actually encouraged not to use anything: https://github.com/goldbergyoni/nodebestpractices#-83-let-the-docker-runtime-handle-replication-and-uptime |
Oh goodness. I missed that line, thank you. I'm used to seeing big alerts at top of readme warning of deprecation I guess :( Thanks for the best practices readme. I've never seen that before. Been around a long time and still using what always worked but just learned or forevers death. Thanks! |
Hello
please future fucntion forever to use :
forever --delay 15 index.js - restart your file for re-connect again from internet.
forever --auto - function , auto detect when file your using to go start.
forever --auto --delay 15 - auto restart your file from after re-connect file and re-detect again .
forever --monitoring -delay 15 , deep active from your restart file and re-connect from VPS\VDS again.
forever --auto -save-file - auto save file for your really time coding about, nodemon your restarting and save your file from your coding.
The text was updated successfully, but these errors were encountered: