aboutsummaryrefslogtreecommitdiff
path: root/issues/server-configuration.md
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-09-27 22:06:31 +0200
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-09-27 22:06:31 +0200
commit0b0320d8f295394e2afc5f0cf012422e8625518b (patch)
treea32512c8d9ce63aa3b9fd92f58468c9e7a8edbb1 /issues/server-configuration.md
parent3981cdc68052c5084c28ade768b635d24242aa6d (diff)
imported issues
Diffstat (limited to 'issues/server-configuration.md')
-rw-r--r--issues/server-configuration.md19
1 files changed, 19 insertions, 0 deletions
diff --git a/issues/server-configuration.md b/issues/server-configuration.md
new file mode 100644
index 0000000..22fbf9a
--- /dev/null
+++ b/issues/server-configuration.md
@@ -0,0 +1,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.