From 89f0a41e8baefddf2c6962a8f0eee71dfd124d21 Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Thu, 9 Dec 2021 11:14:31 +0100 Subject: added issues --- issues/server-configuration.md | 24 ------------------------ 1 file changed, 24 deletions(-) delete mode 100644 issues/server-configuration.md (limited to 'issues/server-configuration.md') diff --git a/issues/server-configuration.md b/issues/server-configuration.md deleted file mode 100644 index dab70b9..0000000 --- a/issues/server-configuration.md +++ /dev/null @@ -1,24 +0,0 @@ -# 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. - -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. -- cgit v1.2.3