docs(cli/README): allign the help message with the latest changes

Author: relu91

packages/cli/README.md

@@ -56,79 +56,44 @@ The `-h` option explains the functionality and also how node-wot can be configur
 The `-h` help option shows the following output:
 
 ```
-Usage: wot-servient [options] [files...]
+Usage: wot-servient [options] [command] [files...]
 
 
 Run a WoT Servient in the current directory.
 
 
 Arguments:
-  files                             script files to execute. If no script is given, all .js files in the current directory are
-                                    loaded. If one or more script is given, these files are loaded instead of the directory.
+  files                           script files to execute. If no script is given, all .js files in the current directory are loaded. If one or more script is given, these files are loaded instead of the directory.
 
 Options:
-  -v, --version                     display node-wot version
-  -i, --inspect [host]:[port]       activate inspector on host:port (default: 127.0.0.1:9229)
-  -ib, --inspect-brk [host]:[port]  activate inspector on host:port (default: 127.0.0.1:9229)
-  -c, --client-only                 do not start any servers (enables multiple instances without port conflicts)
-  -cp, --compiler <module>          load module as a compiler
-  -f, --config-file <file>          load configuration from specified file (default: "wot-servient.conf.json")
-  -p, --config-params <param...>    override configuration parameters [key1:=value1 key2:=value2 ...] (e.g. http.port:=8080)
-  -h, --help                        show this help
-
-wot-servient.conf.json syntax:
+  -v, --version                   display node-wot version
+  -c, --client-only               do not start any servers (enables multiple instances without port conflicts)
+  -ll, --logLevel <string>        choose the desired log level. WARNING: if DEBUG env variable is specified this option gets overridden. (choices: "debug", "info", "warn", "error")
+  -f, --config-file <file>        load configuration from specified file (default: $(pwd)/wot-servient.conf.json
+  -p, --config-params <param...>  override configuration parameters [key1:=value1 key2:=value2 ...] (e.g. http.port:=8080)
+  -h, --help                      show this help
+
+Commands:
+  schema                          prints the json schema for the configuration file
+
+Configuration
+
+Settings can be applied through three methods, in order of precedence (highest to lowest):
+
+1.  Command-Line Parameters (-p path.to.set=value)
+2.  Environment Variables (NODE_WOT_PATH_TO_SET=value) (supports .env files too)
+3.  Configuration File
+
+For the complete list of available configuration fields and their data types, run:
+
+wot-servient schema
+
+In your configuration files you can the following to enable IDE config validation:
+
 {
-    "servient": {
-        "clientOnly": CLIENTONLY,
-        "staticAddress": STATIC,
-        "scriptAction": RUNSCRIPT
-    },
-    "http": {
-        "port": HPORT,
-        "proxy": PROXY,
-        "allowSelfSigned": ALLOW
-    },
-    "mqtt" : {
-        "broker": BROKER-URL,
-        "username": BROKER-USERNAME,
-        "password": BROKER-PASSWORD,
-        "clientId": BROKER-UNIQUEID,
-        "protocolVersion": MQTT_VERSION
-    },
-    "credentials": {
-        THING_ID1: {
-            "token": TOKEN
-        },
-        THING_ID2: {
-            "username": USERNAME,
-            "password": PASSWORD
-        }
-    }
+    "$schema": "./node_modules/@node-wot/cli/dist/wot-servient-schema.conf.json"
+    ...
 }
-
-wot-servient.conf.json fields:
-  CLIENTONLY      : boolean setting if no servers shall be started (default=false)
-  STATIC          : string with hostname or IP literal for static address config
-  RUNSCRIPT       : boolean to activate the 'runScript' Action (default=false)
-  HPORT           : integer defining the HTTP listening port
-  PROXY           : object with "href" field for the proxy URI,
-                                "scheme" field for either "basic" or "bearer", and
-                                corresponding credential fields as defined below
-  ALLOW           : boolean whether self-signed certificates should be allowed
-  BROKER-URL      : URL to an MQTT broker that publisher and subscribers will use
-  BROKER-UNIQUEID : unique id set by MQTT client while connecting to the broker
-  MQTT_VERSION    : number indicating the MQTT protocol version to be used (3, 4, or 5)
-  THING_IDx       : string with TD "id" for which credentials should be configured
-  TOKEN           : string for providing a Bearer token
-  USERNAME        : string for providing a Basic Auth username
-  PASSWORD        : string for providing a Basic Auth password
-  ---------------------------------------------------------------------------
-
-Environment variables must be provided in a .env file in the current working directory.
-
-Example:
-VAR1=Value1
-VAR2=Value2
 ```
 
 Additionally, you can look at [the JSON Schema](https://github.com/eclipse-thingweb/node-wot/blob/master/packages/cli/src/wot-servient-schema.conf.json) to understand possible values for each field.

packages/cli/src/cli.ts

@@ -86,7 +86,7 @@ program
     )
     .option(
         "-f, --config-file <file>",
-        "load configuration from specified file (default: $(pwd)/wot-servient.conf.json",
+        "load configuration from specified file (default: $(pwd)/wot-servient.conf.json)",
         (value, previous) => parseConfigFile(value, previous)
     )
     .option(