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
@@ -1530,7 +1531,7 @@ For instance, if one wants to implement 2 menus (called 'A' and 'B') and only sh
1530
1531
1531
1532
1532
1533
1533
-
## Environment variables ##
1534
+
## Environment variables properties##
1534
1535
1535
1536
The list of environment variables is available through the property system.
1536
1537
@@ -1776,6 +1777,25 @@ For example, the following would define `services.wce.command.start` and `servic
1776
1777
1777
1778
1778
1779
1780
+
# Environment variables #
1781
+
1782
+
ShellAnything default startup behavior can be modified by setting specific pre-defined environment variables. Some features or configuration options can also be enabled or disabled through environment variables. For example, one can define an environment variables to enable verbose logging.
1783
+
1784
+
Most of the time, if a feature can be enabled/disabled from an environment variable and/or a property, the environment variable have priority over internal properties.
1785
+
1786
+
Most environment variables are detected when the application starts. After application startup, if you modify an environment variable you have to log off from windows and log in again for the changes to take effect.
1787
+
1788
+
All ShellAnything environment variables names are prefixed with `SA_`.
1789
+
1790
+
The following table defines the list of pre-defined environment variables for ShellAnything:
| SA_OPTION_LOGGING_VERBOSE | Enables [verbose logging](#verbose-logging) when set to a value that evaluates to [true](#istrue-attribute). |
1795
+
1796
+
1797
+
1798
+
1779
1799
# Plugins #
1780
1800
1781
1801
@@ -2553,6 +2573,22 @@ There are no plan for keeping the log files for more than 5 days.
2553
2573
2554
2574
2555
2575
2576
+
### Verbose logging ###
2577
+
2578
+
The application has a verbose logging mode. When enabled, the application will log additional details. This mode should be disabled by default. It should be temporary enabled because log files will likely contain sensitive information.
2579
+
2580
+
Verbose mode is highly beneficial for debugging because it provides detailed information about the execution of the program. It allows you to see each step and print out intermediate values, helping you identify where things might be going wrong. For example, it is useful for diagnosing the reason for [Visibility / Validity](#visibility--validity) check failures.
2581
+
2582
+
The verbose mode can be enabled (or disabled) with the following option :
2583
+
* Setting property `system.logging.verbose` to a value that evaluates to [true](#istrue-attribute) or [false](#isfalse-attribute).
2584
+
* Setting environment variable `SA_OPTION_LOGGING_VERBOSE` to a value that evaluates to [true](#istrue-attribute) or [false](#isfalse-attribute).
2585
+
2586
+
If both options are specified, the environment variable has priority.
2587
+
2588
+
If no option is specified, verbose mode is disabled.
2589
+
2590
+
2591
+
2556
2592
## Missing ampersand character (`&`) in menus ##
2557
2593
2558
2594
One might be puzzled as to why his menus do not display ampersand character (`&`) properly.
0 commit comments