-~$ keep -h
-keep -h
+~$ keepstore -h
2014/07/24 15:38:27 Keep started: pid 13606
-Usage of keep:
+Usage of keepstore:
-data-manager-token-file="": File with the API token used by the Data Manager. All DELETE requests or GET /index requests must carry this token.
-enforce-permissions=false: Enforce permission signatures on requests.
-listen=":25107": Interface on which to listen for requests, in the format ipaddr:port. e.g. -listen=10.0.1.24:8000. Use -listen=:port to listen on all network interfaces.
+ -never-delete=false: If set, nothing will be deleted. HTTP 405 will be returned for valid DELETE requests.
-permission-key-file="": File containing the secret key for generating and verifying permission signatures.
-permission-ttl=1209600: Expiration time (in seconds) for newly generated permission signatures.
-pid="": Path to write pid file
@@ -35,10 +35,12 @@ Usage of keep:
+If you want access control on your Keep server(s), you should provide a permission key. The @-permission-key-file@ argument should contain the path to a file that contains a single line with a long random alphanumeric string. It should be the same as the @blob_signing_key@ that can be set in the "API server":install-api-server.html config/application.yml file.
+
Prepare one or more volumes for Keep to use. Simply create a /keep directory on all the partitions you would like Keep to use, and then start Keep. For example, using 2 tmpfs volumes: