Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

forever + JSON Configuration Files + set command option

See original GitHub issue

Hi,

How do I make to set command option in forever.json? I need use -c coffee.

I tried:

    "command": "coffee"
    "c: "coffee"
    "COMMAND": "coffee"
    "cmd": "coffee"

And nothing work. This option can be set in json config?

thanks!

Issue Analytics

State:
Created 6 years ago
Reactions:4
Comments:7

Top GitHub Comments

1reaction

muyidscommented, May 19, 2017

when I use forever.json to run app, the command option not work.

{
    "uid": "app-uid",
    "append": true,
    "watch": true,
    "command": "/usr/local/n/versions/node/7.10.0/bin/node",
    "script": "index.js"
}

0reactions

thevirusrelodedcommented, Oct 15, 2018

any update???

Top Results From Across the Web

forever + JSON Configuration Files + set command option #913

Hi,. How do I make to set command option in forever.json? I need use -c coffee . ... And nothing work. This option...

node-forever json config support all options? - Stack Overflow

Firstly, you should check the command line usage. It should be below command: forever start forever/proConfig.json. Secondly, forever does ...

forever - npm

Note: Forever parses JSON configuration files using shush, allowing the use of in-line comments within such files. Multi-App Configuration Files.

Running Node.js scripts continuously using forever

Up to this point, we have used CLI commands to run and manage the Node script. But with forever, we can also configure...

Config Files - Babel.js

Project-wide configs can also be disabled by setting "configFile" to false . File-relative configuration. Babel loads .babelrc.json files, or an equivalent one ...