From 66302e30953b485533ce206fd8437a026a8cee40 Mon Sep 17 00:00:00 2001 From: Roman Dmytrenko Date: Tue, 9 Apr 2024 22:48:51 +0300 Subject: [PATCH] chore(cache): added new username property for redis and update the cache section. --- configuration/overview.mdx | 1 + configuration/storage.mdx | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/configuration/overview.mdx b/configuration/overview.mdx index d502d9c..b467678 100644 --- a/configuration/overview.mdx +++ b/configuration/overview.mdx @@ -297,6 +297,7 @@ export FLIPT_CORS_ALLOWED_ORIGINS="http://localhost:3000 http://localhost:3001" | cache.redis.min_idle_conn | Minimum number of idle connections in the pool | 0 | v1.25.0 | | cache.redis.conn_max_idle_time | Maximum amount of time a connection can be idle | 30m | v1.25.0 | | cache.redis.net_timeout | Network timeout for Redis connections | 0 | v1.25.0 | +| cache.redis.username | Username to access the Redis database | | v1.41.0 | ### Audit Events diff --git a/configuration/storage.mdx b/configuration/storage.mdx index 05a5e48..945e2d6 100644 --- a/configuration/storage.mdx +++ b/configuration/storage.mdx @@ -498,7 +498,7 @@ Flipt has its own custom OCI manifest format (we call them `bundles`), which can Certain OCI registries may require setting the OCI manifest version to something other than the default (`1.1`) to work correctly. -In this case, you can set the `FLIPT_STORAGE_OCI_MANIFEST_VERSION` environment variable or `storage.oci.manifest_version` configuration property to the desired version (e.g. `1.0`). + In this case, you can set the `FLIPT_STORAGE_OCI_MANIFEST_VERSION` environment variable or `storage.oci.manifest_version` configuration property to the desired version (e.g. `1.0`). See [this issue](https://github.com/flipt-io/flipt/issues/2907) for more information. @@ -618,7 +618,7 @@ segments: [] # [Segment] list of Segment definitions Flipt supports both in-memory cache as well as [Redis](https://redis.io/) to enable faster reads and evaluations. Enabling caching has been shown to speed up read performance by -several orders of magnitude. +several orders of magnitude if you are using a relational database. Enabling in-memory caching when running more than one instance of Flipt isn't @@ -631,7 +631,7 @@ Caching works as follows: - All flag reads and evaluation requests go through the cache - Flag cache entries are purged whenever a write to a flag or its variants occur or the TTL expires -- Evaluation cache entries are purged after the TTL expires only +- Cache entries are purged after the TTL expires only - A cache miss will fetch the item from the database and add the item to the cache for the next read - A cache hit will simply return the item from the cache, not interacting with