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
Copy file name to clipboardExpand all lines: docs/deployments/configuration.md
+26-7Lines changed: 26 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,17 +8,36 @@ Some configuration will be populated by default in the config file on install, r
8
8
9
9
## Using the Configuration File and Naming Conventions
10
10
11
-
The configuration elements in `harperdb-config.yaml` use camelcase:`operationsApi`.
11
+
The configuration elements in `harperdb-config.yaml` use camelcase, such as`operationsApi`.
12
12
13
-
To change a configuration value edit the `harperdb-config.yaml` file and save any changes. HarperDB must be restarted for changes to take effect.
13
+
To change a configuration value, edit the `harperdb-config.yaml` file and save any changes. **HarperDB must be restarted for changes to take effect.**
14
14
15
-
Alternately, configuration can be changed via environment and/or command line variables or via the API. To access lower level elements, use underscores to append parent/child elements (when used this way elements are case insensitive):
15
+
Alternatively, all configuration values can also be modified using environment variables, command line arguments, or the operations API via the [`set_configuration` operation](../developers/operations-api/utilities.md#set-configuration).
16
16
17
+
For nested configuration elements, use underscores to represent parent-child relationships. When accessed this way, elements are case-insensitive.
18
+
19
+
For example, to disable logging rotation in the `logging` section:
0 commit comments