minUptime and spinSleepTime warnings even if passed as parameter or in config file
See original GitHub issueWhether specified via config:
{
"path": "./",
"script": "app/index.js",
"minUptime": 1000,
"spinSleepTime": 10000,
"args": [
"--env", "production"
]
}
Or via command line:
> forever start ./forever.json --minUptime 1000 --spinSleepTime 10000
I keep getting these warnings:
warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
Also, minUptime should probably be called minUpTime
with a capital T for consistency.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:5 (3 by maintainers)
Top Results From Across the Web
minUptime and spinSleepTime warnings even if passed as ...
Whether specified via config: { "path": ". ... minUptime and spinSleepTime warnings even if passed as parameter or in config file #870.
Read more >NodeJS Forever package minUptime and spinSleepTime ...
Whenever you set spinSleepTime (with or without minUptime ), your process will restart even if it is considered 'spinning'. forever --spinSleepTime 30000 ...
Read more >forever - npm
A simple CLI tool for ensuring that a given node script runs continuously (i.e. forever). Latest version: 4.0.3, last published: a year ago....
Read more >A simple CLI tool for ensuring that a given node script runs ...
Setup the command to spawn and the options to pass // to that command. ... forEach(function (file) { if (/\.log$/.test(file) && (!runningLogs ||...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The solution is to switch to pm2, which is an actively maintained package unlike this one.
Never mind, I’ve switched to pm2 instead, which still seems to be actively maintained.