You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- If using SSH keys, specify `key_filename` instead of `password`.
102
103
- The remote user must have permissions to run the requested plugins and access required files. If needed, use the `--skip-sudo` argument to skip plugins requiring sudo.
103
104
104
-
### Subcommmands
105
+
### Subcommands
105
106
106
107
Plugins to run can be specified in two ways, using a plugin JSON config file or using the
107
108
'run-plugins' sub command. These two options are not mutually exclusive and can be used together.
@@ -221,7 +222,7 @@ This will generate a new file '/<path_to_node-scraper_logs>/summary.csv' file. T
221
222
contain the results from all 'nodescraper.csv' files from '/<path_to_node-scarper_logs>'.
222
223
223
224
224
-
### Plugin Configs
225
+
### Configs
225
226
A plugin JSON config should follow the structure of the plugin config model defined here.
226
227
The globals field is a dictionary of global key-value pairs; values in globals will be passed to
227
228
any plugin that supports the corresponding key. The plugins field should be a dictionary mapping
@@ -248,7 +249,7 @@ tabular format to the console.
248
249
}
249
250
```
250
251
251
-
1. **'--plugin-configs' command**
252
+
1. Plugin config: **'--plugin-configs' command**
252
253
A plugin config can be used to compare the system data against the config specifications:
253
254
```sh
254
255
node-scraper --plugin-configs plugin_config.json
@@ -306,7 +307,7 @@ Here is an example of a comprehensive plugin config that specifies analyzer args
0 commit comments