You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/developer-lightspeed/con-about-developer-lightspeed.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ This early access program enables customers to share feedback on the user experi
14
14
You can experience {ls-short} Developer Preview by installing the Developer Lightspeed for {product} plugin within an existing {product-very-short} instance.
15
15
Alternatively, if you prefer to test it locally first, you can try {ls-short} using {product-local-very-short}.
Copy file name to clipboardExpand all lines: modules/developer-lightspeed/proc-customizing-the-chat-history-storage.adoc
+12-13Lines changed: 12 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,33 +15,32 @@ If you configure {ls-short} to store chat history using PostgreSQL, prompts and
15
15
====
16
16
17
17
.Procedure
18
-
* When you are using {ls-short} on an Operator-installed {product-very-short} instance, in your {product-very-short} instance ConfigMap, update the `conversation-cache` field as shown in the following example:
19
-
+
18
+
Customize the chat history storage using any of the following methods:
19
+
20
+
* Update your {product-very-short} config file.
21
+
** If you are using {ls-short} on an Operator-installed {product-very-short} instance, update `conversation_cache` in your {product-very-short} ConfigMap.
22
+
** If you are using {ls-short} on a Helm-installed {product-very-short} instance, update `conversation_cache` in your `values.yaml` file.
23
+
+
20
24
[source,yaml]
21
25
----
22
26
conversation_cache:
23
27
type: postgres
24
28
postgres:
25
29
host: _<your_database_host>_
26
30
port: _<your_database_port>_
27
-
dbname: _<your_database_name>_
31
+
db: _<your_database_name>_
28
32
user: _<your_user_name>_
29
-
password_path: postgres_password.txt
33
+
password: _<postgres_password>_
30
34
ca_cert_path: postgres_cert.crt
31
35
ssl_mode: "require"
32
36
----
33
37
34
-
* When you are using {ls-short} on a Helm-installed {product-very-short} instance, in your {product-very-short} instance `values.yaml` file, update the `conversation-cache` field as shown in the following example:
38
+
* Update `conversation_cache` in your {lcs-short} config file:
0 commit comments