Merge branch 'main' into release-rs-aug

Author: rrelledge

content/integrate/redis-data-integration/ingest/data-pipelines/data-pipelines.md

@@ -172,8 +172,6 @@ configuration contains the following data:
     Quarkus [Configuration options](https://quarkus.io/guides/all-config)
     docs for the full set of available properties.
 
-    
-
 ### Targets
 
 Use this section to provide the connection details for the target Redis
@@ -184,6 +182,18 @@ with a unique name that you are free to choose (here, we have used
 `host` and `port` of the server. You can also supply connection credentials
 and TLS/mTLS secrets here if you use them.
 
+{{< note >}}If you specify `localhost` as the address of either the source or target server during
+installation then the connection will fail if the actual IP address changes for the local
+VM. For this reason, we recommend that you don't use `localhost` for the address. However,
+if you do encounter this problem, you can fix it using the following commands on the VM
+that is running RDI itself:
+
+```bash
+sudo k3s kubectl delete nodes --all
+sudo service k3s restart
+```
+{{< /note >}}
+
 ## Job files
 
 You can optionally supply one or more job files that specify how you want to

content/integrate/redis-data-integration/ingest/installation/_index.md

@@ -147,7 +147,8 @@ Follow the steps below for each of your VMs:
 RDI uses a database on your Redis Enterprise cluster to store its state
 information. *This requires Redis Enterprise v6.4 or greater*.
 
-The installer will ask you for cluster admin credentials. You should supply
+The installer gives you instructions to help you create secrets and create your pipeline.
+It will ask you for cluster admin credentials during installation. You should supply
 these if you want the installer to create the RDI database for you.
 
 {{<note>}}The installer does not create the RDI Redis database with
@@ -163,9 +164,19 @@ If you don’t want the installation to create the RDI database for you:
   and TLS.
 - Provide the installation with the required RDI database details.
 
-Once the installation is finished, RDI is ready for use.
+{{< note >}}If you specify `localhost` as the address of the RDI database server during
+installation then the connection will fail if the actual IP address changes for the local
+VM. For this reason, we recommend that you don't use `localhost` for the address. However,
+if you do encounter this problem, you can fix it using the following commands on the VM
+that is running RDI itself:
 
-{{<note>}}RDI gives you instructions to help you create secrets and create your pipeline.{{</note>}}
+```bash
+sudo k3s kubectl delete nodes --all
+sudo service k3s restart
+```
+{{< /note >}}
+
+After the installation is finished, RDI is ready for use.
 
 ## "Silent" installation
 

content/integrate/redis-data-integration/ingest/quick-start-guide.md

@@ -72,6 +72,44 @@ the `config.yaml` file and then edit the following settings:
 
 At this point, the pipeline is ready to deploy.
 
+### Create a context (optional) {#create-context}
+
+To manage and inspect RDI, you can use the
+[`redis-di`]({{< relref "/integrate/redis-data-integration/ingest/reference/cli" >}})
+CLI command, which has several subcommands for different purposes. Most of these commands require you
+to pass at least two options, `--rdi-host` and `--rdi-port`, to specify the host and port of your
+RDI installation. You can avoid typing these options repeatedly by saving the
+information in a *context*.
+
+When you activate a context, the saved values of
+`--rdi-host`, `--rdi-port`, and a few other options are passed automatically whenever
+you use `redis-di`. If you have more than one RDI installation, you can create a context
+for each of them and select the one you want to be active using its unique name.
+
+To create a context, use the
+[`redis-di add-context`]({{< relref "/integrate/redis-data-integration/ingest/reference/cli/redis-di-add-context" >}})
+command:
+
+```bash
+redis-di add-context --rdi-host <host> --rdi-port <port> --cluster-host <Redis DB host> --cluster-api-port <Redis DB API port> --cluster-user <Redis DB username> <unique-context-name>
+```
+
+These options are required but there are also a few others you can save, such as TLS credentials, if
+you are using them (see the
+[reference page]({{< relref "/integrate/redis-data-integration/ingest/reference/cli/redis-di-add-context" >}})
+for details). When you have created a context, use
+[`redis-di set-context`]({{< relref "/integrate/redis-data-integration/ingest/reference/cli/redis-di-set-context" >}})
+to activate it:
+
+```bash
+redis-di set-context <context name>
+```
+
+There are also subcommands to
+[list]({{< relref "/integrate/redis-data-integration/ingest/reference/cli/redis-di-list-contexts" >}})
+and [delete]({{< relref "/integrate/redis-data-integration/ingest/reference/cli/redis-di-delete-context" >}})
+contexts.
+
 ### Deploy the pipeline
 
 You can use Redis Insight to deploy the pipeline by adding a connection to the RDI API
@@ -81,13 +119,15 @@ endpoint (which has the same IP address as your RDI VM and uses port 8083) and t
 redis-di deploy --dir <path to pipeline folder>
 ```
 
-where the path is the one you supplied earlier during the installation. RDI first
+where the path is the one you supplied earlier during the installation. (You may also need
+to supply `--rdi-host` and `--rdi-port` options if you are not using a
+[context](#create-context) as described above.) RDI first
 validates your pipeline and then deploys it if the configuration is correct.
 
 Once the pipeline is running, you can use Redis Insight to view the data flow using the
 pipeline metrics. You can also connect to your target database to see the keys that RDI has written there.
 
-### View RDI's reponse to data changes
+### View RDI's response to data changes
 
 Once the pipeline has loaded a *snapshot* of all the existing data from the source,
 it enters *change data capture (CDC)* mode (see the

content/operate/kubernetes/recommendations/persistent-volumes.md

@@ -33,7 +33,7 @@ spec should include a *persistentSpec* section, in the
 Persistence storage is a requirement for production deployments.
 
 {{< note >}}
-For **production deployments** of Redis Enterprise Cluster on Kubenetes,
+For **production deployments** of Redis Enterprise Cluster on Kubernetes,
 the Redis Enterprise Cluster (REC) must be deployed with persistence enabled.
 The REC deployment files in the [Kubernetes documentation](https://github.com/RedisLabs/redis-enterprise-k8s-docs) contain this declaration by default.
 {{< /note >}}
@@ -53,7 +53,7 @@ Persistent volume claims can be expanded, but not reduced after creation. See [E
 
 {{< note >}}
 We recommend that you omit the volumeSize definition from the REC declaration
-so that the Redis Enterprise Cluster deployment on Kubenetes use the default volume size.
+so that the Redis Enterprise Cluster deployment on Kubernetes use the default volume size.
 {{< /note >}}
 
 ## Storage class name

content/operate/kubernetes/recommendations/sizing-on-kubernetes.md

@@ -50,8 +50,7 @@ To apply the new cluster configuration run:
 
     kubectl apply -f redis-enterprise-cluster.yaml
 
-**Note:** Decreasing the number of nodes is not supported.
-
+{{<warning>}} Decreasing the number of nodes is not supported.{{</warning>}}
 
 ### Sizing compute resources
 

content/operate/rc/_index.md

@@ -9,9 +9,9 @@ description: The fastest way to set up Redis - a fully managed Redis database on
 hideListLinks: true
 weight: 10
 ---
-[Redis Cloud](https://redis.io/cloud/) is a fully managed Redis database offering hosted on major public cloud services.
+[Redis Cloud](https://redis.io/cloud/) is a fully managed database-as-a-service that brings the speed and reliability of Redis to the cloud, offering seamless scalability and high availability for modern applications.
 
-With Redis Cloud, you get all of the features of Redis Enterprise, including:
+With Redis Cloud, you get all of the features of Redis Software, including:
 - [Redis]({{< relref "/develop/" >}}) and [Redis Stack]({{< relref "/operate/oss_and_stack/stack-with-enterprise" >}}) support
 - Linear scalability
 - Instant failover, backups, and recovery

content/operate/rc/cloud-integrations/vercel.md

@@ -0,0 +1,73 @@
+---
+LinkTitle: Vercel Marketplace
+Title: Create a Redis Cloud database with the Vercel integration.
+alwaysopen: false
+categories:
+- docs
+- operate
+- rc
+description: Shows how to create a Redis Cloud database with Vercel integration.
+hideListLinks: true
+weight: 66
+---
+
+The [Redis Cloud Vercel integration](https://vercel.com/marketplace/redis-cloud) lets you create a new Redis database from your Vercel account and connect it to your Vercel project(s).
+
+## Create database
+
+1. Log in to your Vercel account (or create a new one).
+
+1. Navigate to the **Storage** tab and select **Create database**.
+    {{<image filename="/images/rc/vercel-storage-create-database-button.png" alt="Storage - Create Database">}}
+
+1. Under **Storage partners**, select **View all partners**.
+    {{<image filename="/images/rc/vercel-redis-cloud-partners.png" alt="Browse storage" width=40% >}}
+
+1. Find **Redis Cloud** and select **Continue**.
+
+1. In the **Create Database** dialog, select your plan and **Continue**.
+
+    {{<image filename="/images/rc/vercel-create-db-select-plan.png" alt="Create database">}}
+
+    More configuration options are coming soon, such as region selection and multi-zone high availability.
+
+1. Enter your database name or use the automatically generated name.
+
+1. Select **Create**.
+
+## Connect to your database
+
+After creation, you will see your database details. After provisioning is complete, the status will change from `Initializing` to `Available` (you may need to refresh your browser).
+
+{{<image filename="/images/rc/vercel-status-available.png" alt="Vercel database details">}}
+
+You can use the connection string shown under **Quickstart** to [connect to your database]({{<relref "operate/rc/databases/connect">}}).
+
+## Link database to your project
+
+1. Navigate to the **Storage** tab.
+1. Find your new database in the list of your team's databases.
+1. Select **Connect Project**.
+    {{<image filename="/images/rc/vercel-connect-project-button.png" alt="Connect Project button">}}
+1. Choose your project and environments and select **Connect**.
+    {{<image filename="/images/rc/vercel-connect-project.png" alt="Connect project">}}
+
+## Manage your database
+
+From the database details page, you can make edits to your database under **Settings**.
+
+More configuration options are coming soon, including plan changes, multi-zone high availability, and region selection.
+
+### Configure from Redis Cloud
+
+You can also edit some configuration options in Redis Cloud.
+
+From the database detail page, select **Open in Redis Cloud**.
+
+{{<image filename="/images/rc/vercel-open-in-redis-cloud.png" alt="Open in Redis">}}
+
+Your Redis Cloud account is linked to your Vercel account. All your team's Redis databases will be listed under **Databases** in Redis Cloud.
+
+Select your new database to make configuration changes such as passwords or the eviction policy.
+
+{{<note>}} The [eviction policy]({{<relref "/operate/rc/databases/configuration/data-eviction-policies">}}) defaults to `no eviction` for new databases.  You can change this by [editing the database details]({{<relref "/operate/rc/databases/view-edit-database">}}).{{</note>}}

content/operate/rs/databases/configure/_index.md

@@ -149,7 +149,7 @@ You can require [**TLS**]({{< relref "/operate/rs/security/encryption/tls/" >}})
 
 - **Unauthenticated access** - You can access the database as the default user without providing credentials.
 
-- **Password-only authentication** - When you configure a password for your database's default user, all connections to the database must authenticate with the [AUTH command]({{< relref "/commands/auth" >}}.
+- **Password-only authentication** - When you configure a password for your database's default user, all connections to the database must authenticate with the [AUTH command]({{< relref "/commands/auth" >}}).
 
     If you also configure an access control list, connections can specify other users for authentication, and requests are allowed according to the Redis ACLs specified for that user.
 

layouts/partials/tabs/wrapper.html

@@ -72,7 +72,7 @@
                 </div>
             {{ else }}
               <!--<a href='/docs/latest/develop/connect/clients/{{ index $tab "quickstartSlug" }}/' tabindex="1" class="rounded rounded-mx px-3 py-1 text-white text-xs-->
-              <a href='/develop/connect/clients/{{ index $tab "quickstartSlug" }}/' tabindex="1" class="rounded rounded-mx px-3 py-1 text-white text-xs
+              <a href='{{ absURL (print "develop/connect/clients/" (index $tab "quickstartSlug")) }}/' tabindex="1" class="rounded rounded-mx px-3 py-1 text-white text-xs
                                 hover:text-white hover:bg-slate-600 hover:border-transparent focus:outline-none
                                 focus:ring-2 focus:white focus:border-slate-500" title="{{$btnQuickStartText}}">
                 {{ index $tab "title" }} {{ $btnQuickStartText }}