aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-06 16:23:25 +0200
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-10-06 16:23:25 +0200
commita647c47337bab28e4ef6ece587d5087d33294526 (patch)
treedfe542a00f87ba338f78ba79f7eb6bc0158a3cd9
parentcc75064317725f5b4d58b8b364dbf0c9c431ec3e (diff)
expanded server configuration issue
-rw-r--r--issues/server-configuration.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/issues/server-configuration.md b/issues/server-configuration.md
index 22fbf9a..dab70b9 100644
--- a/issues/server-configuration.md
+++ b/issues/server-configuration.md
@@ -17,3 +17,8 @@ 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.
+
+We also need to add better documentation on how to run and configure
+sigsum-log-go. There is a rough start in cmd/sigsum-log-go/README.md. It
+assumes a little bit too much of the reader, and does not document everything
+that is relevant. For example, configuration of sharding is not documented.