-
Notifications
You must be signed in to change notification settings - Fork 288
Update RAG+Redis quickstart guide #372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thank you, @tylerhutcherson ! I'll take a closer look as soon as I can. |
Atleast 1 if not 2 more coming at you later today too :) |
|
Just to set an expectation, I'm currently very busy with sprint work. I'll free up again on Monday next. So, if I don't get to these PRs this week, I will do so the beginning of next week. |
No rush here. Thanks for all of the work you guys do. Hopefully this can add more fuel to your fire :) |
dwdougherty
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @tylerhutcherson . Well done. Thank you very much! Just a few required style changes.
|
|
||
| To build a RAG application with Redis, the following are some general steps: | ||
| 1. **Set up Redis**: Start by setting up a Redis instance and configuring it to handle vector data. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: it's best to use 1. for all numeric bullets. Markdown will number them correctly when processed. It simplifies adding addition future steps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. After I apply these suggestions, I will push a commit to address that too.
Co-authored-by: David Dougherty <david.dougherty@redis.com>
|
Moving to new PR with updated branch. |
This PR introduces a series of recommended updates to the RAG+Redis quickstart to improve language, clarity, and AI-adjacent terminology. Also improves linking to the best internal artifacts we have to help developers get started quickly.
Open to feedback and discussion. Also happy to help do branch renaming (My team has our own JIRA board I could link to with the ID for example).