Skip to content

Commit b21440b

Browse files
committed
Maysuns comments and updated screenshots
1 parent 4129ded commit b21440b

File tree

6 files changed

+14
-19
lines changed

6 files changed

+14
-19
lines changed
132 KB
Loading
-9.41 KB
Loading
-154 KB
Binary file not shown.

modules/developer-lightspeed/con-about-developer-lightspeed.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This early access program enables customers to share feedback on the user experi
1414
You can experience {ls-short} Developer Preview by installing the Developer Lightspeed for {product} plugin within an existing {product-very-short} instance.
1515
Alternatively, if you prefer to test it locally first, you can try {ls-short} using {product-local-very-short}.
1616

17-
image::rhdh-plugins-reference/developer-lightspeed.png[]
17+
image::rhdh-plugins-reference/developer-lightspeed-1-8-0.png[]
1818

1919
.Additional resources
20-
* link:https://github.com/redhat-developer/rhdh-local/blob/main/README.md[{product-local-very-short}]
20+
* link:https://github.com/redhat-developer/rhdh-local/blob/main/README.md[{product-local-very-short}]

modules/developer-lightspeed/proc-customizing-the-chat-history-storage.adoc

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -15,33 +15,32 @@ If you configure {ls-short} to store chat history using PostgreSQL, prompts and
1515
====
1616

1717
.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+
+
2024
[source,yaml]
2125
----
2226
conversation_cache:
2327
type: postgres
2428
postgres:
2529
host: _<your_database_host>_
2630
port: _<your_database_port>_
27-
dbname: _<your_database_name>_
31+
db: _<your_database_name>_
2832
user: _<your_user_name>_
29-
password_path: postgres_password.txt
33+
password: _<postgres_password>_
3034
ca_cert_path: postgres_cert.crt
3135
ssl_mode: "require"
3236
----
3337

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:
3539
+
3640
[source,yaml]
3741
----
3842
conversation_cache:
39-
type: postgres
40-
postgres:
41-
host: _<your_database_host>_
42-
port: _<your_database_port>_
43-
dbname: _<your_database_name>_
44-
user: _<your_user_name>_
45-
password_path: postgres_password.txt
46-
ca_cert_path: postgres_cert.crt
43+
type: "sqlite"
44+
sqlite:
45+
db_path: "/tmp/cache.db"
4746
----

modules/developer-lightspeed/proc-gathering-feedback.adoc

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,6 @@ The collected data resides in the cluster where {product-very-short} and {lcs-sh
1515
+
1616
[source,yaml]
1717
----
18-
llm_providers:
19-
.......
20-
lightspeed_stack:
21-
......
2218
user_data_collection:
2319
feedback_enabled: true
2420
feedback_storage: "/tmp/data/feedback"

0 commit comments

Comments
 (0)