Revisions for dev branch

[Tjatse]

• Reload env graceful and peaceful

• Unify appConf - rename ignoreWatch to ignore_watch

• Documents of Schema

• CLI ignore_watch supports

• Validate Commander options and JSON key-values

• Divide String to Array more intelligence (ESC supports)

  $pm2 start test.js --node-args "port=3001 sitename='first pm2 app'"
  

  The nodeArgs will be

  [
    "port=3001",
    "sitename=first pm2 app"
  ]

  But not

  [
    "port=3001",
    "sitename='first",
    "pm2",
    "app'"
  ]

• Make options briefness and easy configuration

  • min_uptime

    Value of min_uptime could be:

    • Number
      e.g. "min_uptime": 3000 means 3000 milliseconds.
    • String
      In the meantime we are making it briefness and easy configuration: h, m and s, e.g.: "min_uptime": "1h" means one hour, "min_uptime": "5m" means five minutes and "min_uptime": "10s" means ten seconds (At last, it will be transformed into milliseconds).

  • max_memory_restart

    Value of max_memory_restart could be:

    • Number
      e.g. "max_memory_restart": 1024 means 1024 bytes (NOT BITS).
    • String
      In the meantime we are making it briefness and easy configuration: G, M and K, e.g.: "max_memory_restart": "1G" means one gigabytes, "max_memory_restart": "5M" means five megabytes and "max_memory_restart": "10K" means ten kilobytes (At last, it will be transformed into byte(s)).

• Refactor start/restart/reload (CLI, JSON), auto inspect configurations by configured schema, more output information, more humanity.

[Tjatse]

#832 #805 #768

[Tjatse]

Renamed Common.resolveAppPaths to Common.prepareAppConf and made a completely replacement.

[Tjatse]

Everything goes fine now, sorry about the untidy commits ;)

Changes:

• "max_memory_restart": 1024 or --max-memory-restart 1024 means 1024 bytes, not 1024MB ("max_memory_restart": "1024M" instead of it)
• fork/fork_mode will be converted into fork_mode by ConfigValidator, and cluster/cluster_mode will be converted into cluster_mode, so, it's safety to use pm2_env.exec_mode == 'cluster_mode' programmatic, and no need to check it twice like pm2_env.exec_mode == 'cluster_mode' || pm2_env.exec_mode == 'cluster'
• Predications of ConfigValidator are defined in /lib/schema.json and compiled by /lib/tools/Config.js.

[soyuka]

I'll review this as soon as I can @Tjatse looks awesome!

[Tjatse]

@soyuka Thats great, thx!

[soyuka]

Left on purpose?

[Tjatse]

Ops, MISTAKE, forgot to remove!!!

[soyuka]

That's why I'm here for (:

[Unitech]

Awesome PR, thanks! I'm reviewing it

[Unitech]

I made some correction to the code:

allow array and string for watch option -- add some tests for JSON validation
007231a

homogeneize option parsing logic between JSON and CLI execution - cancel JSON execution if there are errors - cleanly exit PM2 CLI with exitCli()
1244da1

State ERRORED_STATUS like stopped/stopping - calling reloadProcessId restart app if stopped or not cluster_mode (fix pull&reload bug) - change exec logic order - flattify Methods.backward
0b3a2c6

Works well now!

[Tjatse]

Great jobs 👍

Unity is strength :p

You guys rock!!