From e0212f3ceca58c0a1b691bfa418593530fab6cc5 Mon Sep 17 00:00:00 2001 From: "eric@statsig.com" <111610731+ealui-statsig@users.noreply.github.com> Date: Fri, 27 Sep 2024 12:17:30 -0700 Subject: [PATCH] Update README.md --- README.md | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index d9df24c..733c8b4 100644 --- a/README.md +++ b/README.md @@ -21,11 +21,12 @@ Usage: server [OPTIONS] Arguments: [possible values: grpc-and-http, grpc, http] - [possible values: local, redis] + [possible values: disabled, local, redis] Options: - --statsd-logging --datadog-logging + --statsd-logging + --statsig-logging --debug-logging -m, --maximum-concurrent-sdk-keys [default: 1000] -p, --polling-interval-in-s [default: 10] @@ -35,13 +36,18 @@ Options: --force-gcp-profiling-enabled -g, --grpc-max-concurrent-streams [default: 500] --clear-external-datastore-on-unauthorized + --x509-server-cert-path + --x509-server-key-path + --x509-client-cert-path -h, --help Print help - -V, --version Print version + -V, --version ``` 1. MODE: This can be configured as grpc or http or grpc-and-http to allow for easy migrations. -2. CACHE: local uses in process memory to cache backup values, while redis, will use redis. Redis - will store the config in a single key entry that ends up being "statsig::{sha256(sdk_key)}". - This allows you read the value back from the SDK data adapter if needed. +2. CACHE: This is for the backup cache. Local uses in process memory to cache backup values, while redis, + will use redis. Redis will store the config in a single key entry that ends up being "statsig::{sha256(sdk_key)}". + This allows you read the value back from the SDK data adapter if needed. We recommend using + redis or disabled. Local was primarily designed for testing and not to be used in production + as it is an exact duplicate of the datastores that are also stored in memory. Additional logging parameters we support: ```