aboutsummaryrefslogtreecommitdiff
path: root/issues/server-configuration.md
blob: 22fbf9a88ffb1d327e0a347117532d0dacf7f6ad (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
# Server configuration
Reported by: ln5

All server configuration is done via command-line arguments.

This is good for configuration settings which last through the lifetime of an
invocation of a log instance, i.e., from launch to Ctrl-C.  Examples:
- `--http_endpoint`
- `--key`.

It is less good for settings that change over time.  Examples:
- `--witnesses`

Reading a configuration file at start and when receiving, say, SIGHUP, is an
alternative.

Implementing a "control port", typically a TCP endpoint, where an administrator
can "program" the log instance is another alternative. Such an interface can
also be used for diagnostics.