docs/8.0/ayanova/docs/ops-config-report-render-browser-path.md

@@ -4,7 +4,7 @@ This optional setting sets the _full_ path to the Chromium web browser executabl
 
 If not set, AyaNova will attempt to automatically download a copy of Chromium to a `.local-chromium` folder under the AyaNova executable folder on first report rendering.
 
-This setting is typically only required for Linux Server operating systems.
+This setting is typically not required to be set.
 
 ## Default
 
@@ -18,6 +18,15 @@ AyaNova expects the report rendering browser path to be provided by a config.jso
 
 The value specified should be a string containing a fully qualified file path to the Chromium browser.
 
+Example config.json entry
+
+```json
+{
+  ...other properties...
+  "AYANOVA_REPORT_RENDER_BROWSER_PATH": "/usr/bin/chromium-browser"
+}
+```
+
 Example command line parameter
 
 `ayanova.exe --AYANOVA_REPORT_RENDER_BROWSER_PATH="/usr/bin/chromium-browser"` )

docs/8.0/ayanova/docs/ops-config-report-rendering-max-instances.md

@@ -38,6 +38,15 @@ AyaNova expects this value to be provided by a config.json property, environment
 The value specified should be a string specifying the value as an integer, for example:
 `5`
 
+Example config.json entry
+
+```json
+{
+  ...other properties...
+  "AYANOVA_REPORT_RENDERING_MAX_INSTANCES": "5"
+}
+```
+
 Example command line parameter
 
 `ayanova.exe --AYANOVA_REPORT_RENDERING_MAX_INSTANCES="5`

docs/8.0/ayanova/docs/ops-config-report-rendering-timeout.md

@@ -14,7 +14,6 @@ When a report is requested to be rendered AyaNova starts the process and makes n
 
 It's important to note that this timeout does not prevent AyaNova from processing a report for any length of time necessary to complete it; this timeout only takes effect if another report is requested to be rendered so if a User has to render a very large report that is known to take longer than the timeout period they would be advised to render that report when no one else is requesting a report (i.e. after hours)
 
-
 The value is specified in **milliseconds** or thousandths of a second. For example a 30 second timeout is 30000 milliseconds.
 
 ## Default
@@ -39,6 +38,15 @@ AyaNova expects this value to be provided by a config.json property, environment
 The value specified should be a string specifying the timeout in **milliseconds**, for example:
 `30000`
 
+Example config.json entry
+
+```json
+{
+  ...other properties...
+  "AYANOVA_REPORT_RENDERING_TIMEOUT": "45000"
+}
+```
+
 Example command line parameter
 
 `ayanova.exe --AYANOVA_REPORT_RENDERING_TIMEOUT="30000`
@@ -52,5 +60,3 @@ Windows
 Linux / MAC
 
 `export AYANOVA_REPORT_RENDERING_TIMEOUT="120000"`
-
-

docs/8.0/ayanova/docs/ops-config-set-superuser-pw.md

@@ -17,6 +17,14 @@ AyaNova expects the override password to be provided by a config.json property,
 The value specified should be a string used to temporarily override the super user password e.g.:
 `Th3RainInSpainFallsMainlyOnTh3Pla1n`
 
+Example config.json entry
+
+```json
+{
+  ...other properties...
+  "AYANOVA_REPORT_RENDERING_TIMEOUT": "Th3RainInSpainFallsMainlyOnTh3Pla1n"
+}
+```
 
 Example command line parameter
 
@@ -31,5 +39,3 @@ Windows
 Linux / MAC
 
 `export AYANOVA_SET_SUPERUSER_PW="Th3RainInSpainFallsMainlyOnTh3Pla1n"`
-
-

docs/8.0/ayanova/docs/ops-config-use-urls.md

@@ -19,6 +19,15 @@ AyaNova expects the PORT and URL to be provided by a config.json property, envir
 The value specified should be a string of one or more semicolon separated values, for example:
 `http://*:5000;http://localhost:5001;https://hostname:5002`
 
+Example config.json entry
+
+```json
+{
+  ...other properties...
+  "AYANOVA_USE_URLS": "http://*:49152"
+}
+```
+
 Example command line parameter
 
 `ayanova.exe --AYANOVA_USE_URLS="http://*:5000"`