Merge branch 'main' into DOC-4657

Author: cmilesb

content/commands/bitpos/index.md

@@ -104,16 +104,25 @@ Non-existent keys are treated as empty strings.
 
 ## Examples
 
-{{% redis-cli %}}
-SET mykey "\xff\xf0\x00"
-BITPOS mykey 0
-SET mykey "\x00\xff\xf0"
-BITPOS mykey 1 0
-BITPOS mykey 1 2
-BITPOS mykey 1 2 -1 BYTE
-BITPOS mykey 1 7 15 BIT
-set mykey "\x00\x00\x00"
-BITPOS mykey 1
-BITPOS mykey 1 7 -3 BIT
-{{% /redis-cli %}}
-
+```redis
+redis> SET mykey "\xff\xf0\x00"
+OK
+redis> BITPOS mykey 0
+(integer) 12
+redis> SET mykey "\x00\xff\xf0"
+OK
+redis> BITPOS mykey 1 0
+(integer) 8
+redis> BITPOS mykey 1 2
+(integer) 16
+redis> BITPOS mykey 1 2 -1 BYTE
+(integer) 16
+redis> BITPOS mykey 1 7 15 BIT
+(integer) 8
+redis> set mykey "\x00\x00\x00"
+OK
+redis> BITPOS mykey 1
+(integer) -1
+redis> BITPOS mykey 1 7 -3 BIT
+(integer) -1
+```

content/develop/tools/insight/release-notes/v.2.64.0.md

@@ -0,0 +1,33 @@
+---
+Title: Redis Insight v2.64.0, December 2024
+linkTitle: v2.64.0 (December 2024)
+date: 2024-12-19 00:00:00 +0000
+description: Redis Insight v2.64
+weight: 1
+
+---
+## 2.64 (December 2024)
+This is the General Availability (GA) release of Redis Insight 2.64.
+
+### Highlights 
+- Improved the database connections list and simplified the connection form, delivering a cleaner, more intuitive UI for improved focus.
+- New in-app reminders to prevent your free Redis Cloud database from being deleted due to inactivity, ensuring you can make the most of it to test your ideas.
+
+### Details
+
+**Features and improvements**
+- [#4088](https://github.com/RedisInsight/RedisInsight/pull/4088), [#4078](https://github.com/RedisInsight/RedisInsight/pull/4078), [#4094](https://github.com/RedisInsight/RedisInsight/pull/4094) Improved the database connections list and simplified the connection form, delivering a cleaner, more intuitive UI for improved focus.
+- [#4189](https://github.com/RedisInsight/RedisInsight/pull/4189), [#4191](https://github.com/RedisInsight/RedisInsight/pull/4191) New in-app reminders notify you before your free Redis Cloud database is deleted due to inactivity, ensuring you can make the most of it to test your ideas.
+- [#4204](https://github.com/RedisInsight/RedisInsight/pull/4204), [#4196](https://github.com/RedisInsight/RedisInsight/pull/4196), [#4202](https://github.com/RedisInsight/RedisInsight/pull/4202) Various vulnerabilities have been fixed.
+
+**Bugs**
+- [#4194](https://github.com/RedisInsight/RedisInsight/pull/4194) Resolved an [issue](https://github.com/RedisInsight/RedisInsight/issues/4186) where modifying a JSON value inadvertently converted strings into numbers.
+
+**SHA-256 Checksums**
+| Package | SHA-256 |
+|--|--|
+| Windows | iYZbKsFtz/Ua4qeBdeHIRtZRiA1I50R3yY1t3VUD2cn94EpZLR5Xz3lK3yRxA85PxJaHjrWljyGliZv0OX0KBg== |
+| Linux AppImage | ToEFW8wVLI8oFoc/puzf2Cwoff8gBTsIxEsGjQRZq5D5BgrE3muxtuEQto3J2RiRbadGAZx6AZPh75WVJ0DKRw== |
+| Linux Debian| /k6jgfzDSRJ0yWmbtxpD5WG2i9wGUZ4r2AexDz6rUOLyZMqQPJUKEKuonprFvHZp+PUW/EtSWc436IFykBVmsQ== |
+| MacOS Intel | PrbRc+ju0UKxr4huP7Xl9Sq0fH0XaxUtydW86rAYepEAADUADsAYV2lB8gO7Ohs9ukJ7mXBEU7OJWRqJGLhxHg== |
+| MacOS Apple silicon | E6kTbnkoW3eji/v7WVrnwqlEKk444+hxiFqt56r8J+zAHhmX9dlNd7y37xdJlQ82FZ9QOIIMsN5Z0N+bgRisuw== |

content/develop/tools/redis-for-vscode/release-notes/v1.2.0.md

@@ -0,0 +1,35 @@
+---
+Title: Redis for VS Code v1.2.0, December 2024
+linkTitle: v1.2.0 (December 2024)
+date: 2024-12-19 00:00:00 +0000
+description: Redis for VS Code v1.2
+weight: 99
+---
+
+## 1.2.0 (December 2024)
+
+This is the General Availability (GA) release of Redis for VS Code 1.2.
+
+### Headlines
+* Work with keys across multiple database indexes, which are automatically discovered and displayed in the database list.
+* Support for adding multiple elements to the head or tail of Redis lists, for both new and existing keys.
+* Auto-refresh the list of keys and key values with a customizable timer.
+* Delete and update previously added CA and client certificates to keep them updated.
+
+### Details
+
+- [#223](https://github.com/RedisInsight/Redis-for-VS-Code/pull/223) Work with keys across multiple database indexes. Database indexes with keys are automatically discovered and displayed in the database list. 
+- [#207](https://github.com/RedisInsight/Redis-for-VS-Code/pull/207) Support for adding multiple elements to the head or tail of Redis lists for new and existing key.
+- [#226](https://github.com/RedisInsight/Redis-for-VS-Code/pull/226) Auto-refresh the list of keys and key values with a customizable timer. To do so, enable the Auto-refresh mode by clicking the control next to the Refresh button and setting the refresh rate.
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Ability to delete previously added CA and Client certificates to keep them up-to-date.
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Enhanced both the Java and PHP serialized formatters: the Java formatter now supports date and time data, while the PHP formatter includes UTF-8 encoding for better handling of special characters and multi-language data.
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Keep databases and the list of keys [expanded](https://github.com/RedisInsight/Redis-for-VS-Code/issues/217) after navigating away.
+- [#226](https://github.com/RedisInsight/Redis-for-VS-Code/pull/226) New users can optionally encrypt sensitive data, such as connection certificates and passwords. Existing users can enable encryption by deleting the ~/.redis-for-vscode/redisinsight.db file and re-adding their database connections.
+
+**Bugs**
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Resolved an issue where large integers in JSON keys were being rounded, ensuring data integrity.
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Saved SNI and SSH connection information for newly added database connections.
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Fixed an issue to display multiple hash fields when expanding a hash value.
+
+### Get started with Redis for VS Code
+Install the extension from the [Visual Studio Code Marketplace](https://marketplace.visualstudio.com/items?itemName=redis.redis-for-vscode) to use it.

content/develop/use/patterns/distributed-locks.md

@@ -56,7 +56,6 @@ already available that can be used for reference.
 * [ScarletLock](https://github.com/psibernetic/scarletlock) (C# .NET implementation with configurable datastore).
 * [Redlock4Net](https://github.com/LiZhenNet/Redlock4Net) (C# .NET implementation).
 * [node-redlock](https://github.com/mike-marcacci/node-redlock) (NodeJS implementation). Includes support for lock extension.
-* [simple-redis-mutex](https://github.com/AmrSaber/simple-redis-mutex) (Node.js implementation) Available as an [NPM package](https://www.npmjs.com/package/simple-redis-mutex).
 * [Deno DLM](https://github.com/oslabs-beta/Deno-Redlock) (Deno implementation)
 * [Rslock](https://github.com/hexcowboy/rslock) (Rust implementation). Includes async and lock extension support.
 

content/embeds/rc-create-db-first-steps.md

@@ -8,15 +8,4 @@ To create a database in your Redis Cloud account:
 
     {{<image filename="images/rc/button-database-new.png" alt="The New Database button creates a new database." width="120px">}}
 
-    This displays the **Create database** screen.
-
-3. Select your Redis use case. There are four pre-defined use cases:
-
-    {{<image filename="images/rc/create-database-redis-use-cases.png" alt="The Redis Use case panel">}}
-
-    - **Cache**: Stores short-term or volatile data. Can be used for session management, semantic cache, session store, and other uses where data is short-lived.
-    - **Database**: Stores durable and consistent data. Can be used for document databases, feature storage, gaming leaderboards, durable caches, and other uses where your data needs to be highly available and persistent.
-    - **Vector search**: Manages and manipulates vector data. Can be used for Generative AI, recommendation systems, visual search, and other uses where you can search and query your data.
-    - **Custom**: If your Redis use case doesn't match any of the other use cases, you can choose this option to customize all of your settings.
-
-    Select the use case that best matches your Redis use case. You can always change the settings later. 
+    This displays the **Create database** screen.

content/embeds/rc-create-db-use-cases.md

@@ -0,0 +1,10 @@
+3. Select your Redis use case. There are four pre-defined use cases:
+
+    {{<image filename="images/rc/create-database-redis-use-cases.png" alt="The Redis Use case panel">}}
+
+    - **Cache**: Stores short-term or volatile data. Can be used for session management, semantic cache, session store, and other uses where data is short-lived.
+    - **Database**: Stores durable and consistent data. Can be used for document databases, feature storage, gaming leaderboards, durable caches, and other uses where your data needs to be highly available and persistent.
+    - **Vector search**: Manages and manipulates vector data. Can be used for Generative AI, recommendation systems, visual search, and other uses where you can search and query your data.
+    - **Custom**: If your Redis use case doesn't match any of the other use cases, you can choose this option to customize all of your settings.
+
+    Select the use case that best matches your Redis use case. You can always change the settings later. 

content/integrate/prometheus-with-redis-enterprise/_index.md

@@ -32,6 +32,7 @@ You can use Prometheus and Grafana to:
 {{<image filename="images/rs/grafana-prometheus.png" alt="Graphic showing how Prometheus and Grafana collect and display data from a Redis Enterprise Cluster. Prometheus collects metrics from the Redis Enterprise cluster, and Grafana queries those metrics for visualization.">}}
 
 In each cluster, the metrics_exporter process exposes Prometheus metrics on port 8070.
+Redis Enterprise version 7.8.2 introduces a preview of the new metrics stream engine that exposes the v2 Prometheus scraping endpoint at `https://<IP>:8070/v2`.
 
 ## Quick start
 
@@ -80,7 +81,7 @@ We recommend running Prometheus in Docker only for development and testing.
         tls_config:
           insecure_skip_verify: true
         static_configs:
-          - targets: ["<cluster_name>:8070"]
+          - targets: ["<cluster_name>:8070"] # For v2, use ["<cluster_name>:8070/v2"]
     ```
 
 1. Set up your Prometheus and Grafana servers.

content/integrate/redis-data-integration/installation/install-vm.md

@@ -232,11 +232,15 @@ silent install configuration:
 title = "RDI Silent Installer Config"
 
 scaffold = true
+db_index = 4
 deploy_directory = "/opt/rdi/config"
 
-# Needed if the installer detects a DNS resolver with a loopback address
-# as an upstream DNS server
-nameservers = ["8.8.8.8", "8.8.4.4"]
+# Upstream DNS servers. This is needed if the installer detects a DNS resolver 
+# with a loopback address as an upstream DNS server.
+# nameservers = ["8.8.8.8", "8.8.4.4"]
+
+# HTTPS port you want to expose the RDI API on, if different from 443.
+# https_port = 5443
 
 [rdi.database]
 host = "localhost"
@@ -266,7 +270,8 @@ The sections below describe the properties in more detail.
 | `scaffold` | Do you want to enable [scaffolding]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-scaffold" >}}) during the install? (true/false) |
 | `db_index` | Integer to specify the source database type for scaffolding. The options are 2 (MySQL/MariaDB), 3 (Oracle), 4 (PostgreSQL), and 5 (SQL Server). |
 | `deploy_directory` | Path to the directory where you want to store the RDI configuration. |
-| `nameservers` | This is needed if the installer detects a DNS resolver with a loopback address as an upstream DNS server (for example, `nameservers = ["8.8.8.8", "8.8.4.4"]`). |
+| `nameservers` | Upstream DNS servers. This is needed if the installer detects a DNS resolver with a loopback address as an upstream DNS server (for example, `nameservers = ["8.8.8.8", "8.8.4.4"]`). |
+| `https_port` | HTTPS port you want to expose the RDI API on, if different from 443. |
 
 #### `rdi.database`
 

content/operate/kubernetes/7.4.6/security/manage-rec-credentials.md

@@ -155,4 +155,4 @@ If you store your secrets with Hashicorp Vault, update the secret for the REC cr
 username:<desired_username>, password:<desired_password>
 ```
 
-For more information about Vault integration with the Redis Enterprise Cluster see [Integrating Redis Enterprise for Kubernetes with Hashicorp Vault](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/65eba63a6aac69455a691652218e28b0873e4de3/vault/README.md).
+For more information about Vault integration with the Redis Enterprise Cluster see [Integrating Redis Enterprise for Kubernetes with Hashicorp Vault](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/vault/README.md).

content/operate/kubernetes/security/manage-rec-credentials.md

@@ -154,4 +154,4 @@ If you store your secrets with Hashicorp Vault, update the secret for the REC cr
 username:<desired_username>, password:<desired_password>
 ```
 
-For more information about Vault integration with the Redis Enterprise Cluster see [Integrating Redis Enterprise for Kubernetes with Hashicorp Vault](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/65eba63a6aac69455a691652218e28b0873e4de3/vault/README.md).
+For more information about Vault integration with the Redis Enterprise Cluster see [Integrating Redis Enterprise for Kubernetes with Hashicorp Vault](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/vault/README.md).