mirror of
https://git.mirrors.martin98.com/https://github.com/infiniflow/ragflow.git
synced 2025-04-24 07:00:02 +08:00
Fixed a docusaurus display issue (#2340)
### What problem does this PR solve? ### Type of change - [x] Documentation Update
This commit is contained in:
parent
c57cc0769b
commit
7c8f159751
@ -3,6 +3,6 @@
|
||||
"position": 3,
|
||||
"link": {
|
||||
"type": "generated-index",
|
||||
"description": "Agentic RAG-specific User Guides"
|
||||
"description": "RAGFlow v0.8.0 introduces an Agentic RAG mechanism, featuring a no-code workflow editor on the front end and a comprehensive graph-based task orchestration framework on the back end."
|
||||
}
|
||||
}
|
||||
|
@ -3,9 +3,9 @@ sidebar_position: 1
|
||||
slug: /agentic_rag_introduction
|
||||
---
|
||||
|
||||
# A brief introduction
|
||||
# Introduction to Agentic RAG
|
||||
|
||||
Agents and RAG are complementary techniques, each enhancing the other’s capabilities in business applications. RAGFlow v0.8.0 introduces an agent mechanism, featuring a no-code workflow editor on the front end and a comprehensive graph-based task orchestration framework on the back end. Built on top of RAGFlow's existing RAG solutions, this mechanism aims to orchestrate search technologies such as query intent classification, conversation leading, and query rewriting to:
|
||||
Agents and RAG are complementary techniques, each enhancing the other’s capabilities in business applications. RAGFlow v0.8.0 introduces an Agentic RAG mechanism, featuring a no-code workflow editor on the front end and a comprehensive graph-based task orchestration framework on the back end. This mechanism is built on top of RAGFlow's existing RAG solutions and aims to orchestrate search technologies such as query intent classification, conversation leading, and query rewriting to:
|
||||
|
||||
- Provide higher retrievals and,
|
||||
- Accommodate more complex scenarios.
|
||||
|
@ -340,8 +340,8 @@ This exception occurs when starting up the RAGFlow server. Try the following:
|
||||

|
||||
|
||||
1. Ensure that the RAGFlow server can access the base URL.
|
||||
2. Do not forget to append **/v1/** to **http://IP:port**:
|
||||
**http://IP:port/v1/**
|
||||
2. Do not forget to append `/v1/` to `http://IP:port`:
|
||||
`http://IP:port/v1/`
|
||||
|
||||
#### 4.16 `FileNotFoundError: [Errno 2] No such file or directory`
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user