langchain/docs
Michael Gorham 3b0226b2c6
docs: Update redis_chat_message_history.ipynb (#16344)
## Problem
Spent several hours trying to figure out how to pass
`RedisChatMessageHistory` as a `GetSessionHistoryCallable` with a
different REDIS hostname. This example kept connecting to
`redis://localhost:6379`, but I wanted to connect to a server not hosted
locally.

## Cause
Assumption the user knows how to implement `BaseChatMessageHistory` and
`GetSessionHistoryCallable`

## Solution
Update documentation to show how to explicitly set the REDIS hostname
using a lambda function much like the MongoDB and SQLite examples.
2024-01-22 21:59:59 -08:00
..
api_reference docs: bump sphinx>=5 (#16162) 2024-01-17 12:57:34 -08:00
docs docs: Update redis_chat_message_history.ipynb (#16344) 2024-01-22 21:59:59 -08:00
scripts docs: fix llm/chat_model tables (#15716) 2024-01-08 11:40:35 -08:00
src docs[patch]: fix zoom (#14786) 2023-12-15 17:46:12 -08:00
static docs: add tool use diagrams (#16207) 2024-01-18 07:59:54 -08:00
.local_build.sh update chain docs (#15495) 2024-01-05 09:15:00 -08:00
babel.config.js Restructure docs (#11620) 2023-10-10 12:55:19 -07:00
code-block-loader.js Restructure docs (#11620) 2023-10-10 12:55:19 -07:00
docusaurus.config.js docs: add changelog (#15606) 2024-01-07 08:34:34 -08:00
package-lock.json docs[patch]: search experiment (#14254) 2023-12-04 16:58:26 -08:00
package.json docs[patch]: search experiment (#14254) 2023-12-04 16:58:26 -08:00
README.md docs: developer docs (#14776) 2023-12-17 12:55:49 -08:00
settings.ini Restructure docs (#11620) 2023-10-10 12:55:19 -07:00
sidebars.js docs: add LangGraph (#15682) 2024-01-08 08:38:14 -08:00
vercel_build.sh docs: add LangGraph (#15682) 2024-01-08 08:38:14 -08:00
vercel_requirements.txt infra: docs build install community editable (#14739) 2023-12-14 16:13:09 -08:00
vercel.json core[patch], community[patch], langchain[patch], docs: Update SQL chains/agents/docs (#16168) 2024-01-22 08:19:08 -08:00

LangChain Documentation

For more information on contributing to our documentation, see the Documentation Contributing Guide