Skip to content

Commit f857e2b

Browse files
Merge pull request #158 from HarperDB/update-config-naming-con
Update configuration file and naming conventions section
2 parents 83bd256 + 9e29af0 commit f857e2b

File tree

1 file changed

+26
-7
lines changed

1 file changed

+26
-7
lines changed

docs/deployments/configuration.md

Lines changed: 26 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,17 +8,36 @@ Some configuration will be populated by default in the config file on install, r
88

99
## Using the Configuration File and Naming Conventions
1010

11-
The configuration elements in `harperdb-config.yaml` use camelcase: `operationsApi`.
11+
The configuration elements in `harperdb-config.yaml` use camelcase, such as `operationsApi`.
1212

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.**
1414

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).
1616

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:
20+
21+
```yaml
22+
logging:
23+
rotation:
24+
enabled: false
1725
```
18-
- Environment variables: `OPERATIONSAPI_NETWORK_PORT=9925`
19-
- Command line variables: `--OPERATIONSAPI_NETWORK_PORT 9925`
20-
- Calling `set_configuration` through the API: `operationsApi_network_port: 9925`
21-
```
26+
27+
You could apply this change using:
28+
* Environment variable: `LOGGING_ROTATION_ENABLED=false`
29+
* Command line variable: `--LOGGING_ROTATION_ENABLED false`
30+
* Operations API (`set_configuration`): `logging_rotation_enabled: false`
31+
32+
To change the `port` in the `http` section, use:
33+
* Environment variable: `HTTP_PORT=<port>`
34+
* Command line variable: `--HTTP_PORT <port>`
35+
* Operations API (`set_configuration`): `http_port: <port>`
36+
37+
To set the `operationsApi.network.port` to `9925`, use:
38+
* Environment variable: `OPERATIONSAPI_NETWORK_PORT=9925`
39+
* Command line variable: `--OPERATIONSAPI_NETWORK_PORT 9925`
40+
* Operations API (`set_configuration`): `operationsApi_network_port: 9925`
2241

2342
_Note: Component configuration cannot be added or updated via CLI or ENV variables._
2443

0 commit comments

Comments
 (0)