2025-01-17 18:22:02 +08:00
|
|
|
|
<div align="center">
|
2026-03-16 14:44:39 +08:00
|
|
|
|
<a href="https://cloud.ragflow.io/">
|
2025-10-15 11:46:24 +08:00
|
|
|
|
<img src="web/src/assets/logo-with-text.svg" width="350" alt="ragflow logo">
|
2025-01-17 18:22:02 +08:00
|
|
|
|
</a>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<p align="center">
|
2025-05-28 18:31:50 +08:00
|
|
|
|
<a href="./README.md"><img alt="README in English" src="https://img.shields.io/badge/English-DFE0E5"></a>
|
|
|
|
|
|
<a href="./README_zh.md"><img alt="简体中文版自述文件" src="https://img.shields.io/badge/简体中文-DFE0E5"></a>
|
2025-06-17 18:01:56 +08:00
|
|
|
|
<a href="./README_tzh.md"><img alt="繁體版中文自述文件" src="https://img.shields.io/badge/繁體中文-DBEDFA"></a>
|
2025-05-28 18:31:50 +08:00
|
|
|
|
<a href="./README_ja.md"><img alt="日本語のREADME" src="https://img.shields.io/badge/日本語-DFE0E5"></a>
|
|
|
|
|
|
<a href="./README_ko.md"><img alt="한국어" src="https://img.shields.io/badge/한국어-DFE0E5"></a>
|
2026-05-06 11:57:29 +08:00
|
|
|
|
<a href="./README_fr.md"><img alt="README en Français" src="https://img.shields.io/badge/Français-DFE0E5"></a>
|
2025-05-28 18:31:50 +08:00
|
|
|
|
<a href="./README_id.md"><img alt="Bahasa Indonesia" src="https://img.shields.io/badge/Bahasa Indonesia-DFE0E5"></a>
|
|
|
|
|
|
<a href="./README_pt_br.md"><img alt="Português(Brasil)" src="https://img.shields.io/badge/Português(Brasil)-DFE0E5"></a>
|
2026-03-02 19:10:11 +08:00
|
|
|
|
<a href="./README_ar.md"><img alt="README in Arabic" src="https://img.shields.io/badge/Arabic-DFE0E5"></a>
|
docs: add Turkish README translation (README_tr.md) (#13750)
## Summary
Add a complete Turkish translation of the README and include a Turkish
language badge across all existing README files.
## Changes
- **New file**: `README_tr.md` - Full Turkish translation of README.md,
covering all sections (What is RAGFlow, Demo, Latest Updates, Key
Features, System Architecture, Get Started, Configurations, Docker
Image, Development from Source, Documentation, Roadmap, Community,
Contributing)
- **Updated 9 existing README files** (README.md, README_zh.md,
README_tzh.md, README_ja.md, README_ko.md, README_id.md,
README_pt_br.md, README_fr.md, README_ar.md) to include the Turkish
language badge in the language selector
## Impact
- 10 files changed, 417 insertions
- Follows the same structure and conventions as other language-specific
README files (README_ja.md, README_ko.md, etc.)
- Turkish badge uses the same styling pattern (highlighted with DBEDFA
in README_tr.md, standard DFE0E5 in others)
---------
Co-authored-by: bakiburakogun <bakiburakogun@users.noreply.github.com>
2026-03-24 14:00:48 +03:00
|
|
|
|
<a href="./README_tr.md"><img alt="Türkçe README" src="https://img.shields.io/badge/Türkçe-DFE0E5"></a>
|
2025-01-17 18:22:02 +08:00
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
|
|
<p align="center">
|
|
|
|
|
|
<a href="https://x.com/intent/follow?screen_name=infiniflowai" target="_blank">
|
|
|
|
|
|
<img src="https://img.shields.io/twitter/follow/infiniflow?logo=X&color=%20%23f5f5f5" alt="follow on X(Twitter)">
|
|
|
|
|
|
</a>
|
2026-03-16 14:44:39 +08:00
|
|
|
|
<a href="https://cloud.ragflow.io" target="_blank">
|
2026-05-06 11:57:29 +08:00
|
|
|
|
<img alt="Static Badge" src="https://img.shields.io/badge/Get-Started-4e6b99">
|
2025-01-17 18:22:02 +08:00
|
|
|
|
</a>
|
|
|
|
|
|
<a href="https://hub.docker.com/r/infiniflow/ragflow" target="_blank">
|
2026-06-29 09:40:45 +08:00
|
|
|
|
<img src="https://img.shields.io/docker/pulls/infiniflow/ragflow?label=Docker%20Pulls&color=0db7ed&logo=docker&logoColor=white&style=flat-square" alt="docker pull infiniflow/ragflow:v0.26.2">
|
2025-01-17 18:22:02 +08:00
|
|
|
|
</a>
|
|
|
|
|
|
<a href="https://github.com/infiniflow/ragflow/releases/latest">
|
|
|
|
|
|
<img src="https://img.shields.io/github/v/release/infiniflow/ragflow?color=blue&label=Latest%20Release" alt="Latest Release">
|
|
|
|
|
|
</a>
|
|
|
|
|
|
<a href="https://github.com/infiniflow/ragflow/blob/main/LICENSE">
|
|
|
|
|
|
<img height="21" src="https://img.shields.io/badge/License-Apache--2.0-ffffff?labelColor=d4eaf7&color=2e6cc4" alt="license">
|
|
|
|
|
|
</a>
|
2025-05-28 09:29:33 +08:00
|
|
|
|
<a href="https://deepwiki.com/infiniflow/ragflow">
|
|
|
|
|
|
<img alt="Ask DeepWiki" src="https://deepwiki.com/badge.svg">
|
|
|
|
|
|
</a>
|
2025-01-17 18:22:02 +08:00
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
|
|
<h4 align="center">
|
2026-05-06 11:57:29 +08:00
|
|
|
|
<a href="https://cloud.ragflow.io">Cloud</a> |
|
2025-01-17 18:22:02 +08:00
|
|
|
|
<a href="https://ragflow.io/docs/dev/">Document</a> |
|
2025-12-31 12:49:42 +08:00
|
|
|
|
<a href="https://github.com/infiniflow/ragflow/issues/12241">Roadmap</a> |
|
2026-05-06 11:57:29 +08:00
|
|
|
|
<a href="https://discord.gg/NjYzJD3GM3">Discord</a>
|
2025-01-17 18:22:02 +08:00
|
|
|
|
</h4>
|
|
|
|
|
|
|
2025-10-29 00:34:39 +08:00
|
|
|
|
<div align="center" style="margin-top:20px;margin-bottom:20px;">
|
|
|
|
|
|
<img src="https://raw.githubusercontent.com/infiniflow/ragflow-docs/refs/heads/image/image/ragflow-octoverse.png" width="1200"/>
|
|
|
|
|
|
</div>
|
2025-05-28 18:31:50 +08:00
|
|
|
|
|
|
|
|
|
|
<div align="center">
|
|
|
|
|
|
<a href="https://trendshift.io/repositories/9064" target="_blank"><img src="https://trendshift.io/api/badge/repositories/9064" alt="infiniflow%2Fragflow | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
<details open>
|
|
|
|
|
|
<summary><b>📕 目錄</b></summary>
|
|
|
|
|
|
|
|
|
|
|
|
- 💡 [RAGFlow 是什麼？](#-RAGFlow-是什麼)
|
2026-05-06 11:57:29 +08:00
|
|
|
|
- 🎮 [快速開始](#-快速開始)
|
2025-05-28 18:31:50 +08:00
|
|
|
|
- 📌 [近期更新](#-近期更新)
|
|
|
|
|
|
- 🌟 [主要功能](#-主要功能)
|
|
|
|
|
|
- 🔎 [系統架構](#-系統架構)
|
2026-05-06 11:57:29 +08:00
|
|
|
|
- 🎬 [自行架設](#-自行架設)
|
2025-05-28 18:31:50 +08:00
|
|
|
|
- 🔧 [系統配置](#-系統配置)
|
|
|
|
|
|
- 🔨 [以原始碼啟動服務](#-以原始碼啟動服務)
|
|
|
|
|
|
- 📚 [技術文檔](#-技術文檔)
|
|
|
|
|
|
- 📜 [路線圖](#-路線圖)
|
|
|
|
|
|
- 🏄 [貢獻指南](#-貢獻指南)
|
|
|
|
|
|
- 🙌 [加入社區](#-加入社區)
|
|
|
|
|
|
- 🤝 [商務合作](#-商務合作)
|
|
|
|
|
|
|
|
|
|
|
|
</details>
|
|
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
## 💡 RAGFlow 是什麼？
|
|
|
|
|
|
|
2025-12-31 20:07:40 +08:00
|
|
|
|
[RAGFlow](https://ragflow.io/) 是一款領先的開源 [RAG](https://ragflow.io/basics/what-is-rag)（Retrieval-Augmented Generation）引擎，通過融合前沿的 RAG 技術與 Agent 能力，為大型語言模型提供卓越的上下文層。它提供可適配任意規模企業的端到端 RAG 工作流，憑藉融合式[上下文引擎](https://ragflow.io/basics/what-is-agent-context-engine)與預置的 Agent 模板，助力開發者以極致效率與精度將複雜數據轉化為高可信、生產級的人工智能系統。
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
2026-05-06 11:57:29 +08:00
|
|
|
|
## 🎮 快速開始
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
2026-05-06 11:57:29 +08:00
|
|
|
|
請登入網址 [https://cloud.ragflow.io](https://cloud.ragflow.io) 試用雲服務。
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
<div align="center" style="margin-top:20px;margin-bottom:20px;">
|
2025-08-01 20:42:12 +08:00
|
|
|
|
<img src="https://raw.githubusercontent.com/infiniflow/ragflow-docs/refs/heads/image/image/chunking.gif" width="1200"/>
|
|
|
|
|
|
<img src="https://raw.githubusercontent.com/infiniflow/ragflow-docs/refs/heads/image/image/agentic-dark.gif" width="1200"/>
|
2025-01-17 18:22:02 +08:00
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
## 🔥 近期更新
|
|
|
|
|
|
|
Feat: chat channels — connect assistants to external messaging bots (#15850)
### What problem does this PR solve?
#15844
Adds a **Chat channels** capability so a RAGFlow assistant (Dialog) can
be exposed as a bot on external messaging platforms (Feishu/Lark,
Discord, Telegram, Slack, WeCom, LINE, etc.). An admin configures a bot
in the UI, connects it to an assistant, and inbound messages are
answered from that assistant's knowledge base — replies are delivered
back on the channel.
**Feishu/Lark is implemented and tested end-to-end.** Discord, Telegram,
LINE, and WeCom are scaffolded against the same interface; the remaining
listed channels are tracked as follow-ups.
### Design
**Backend**
- New `chat_channel` table (`tenant_id`, `name`, `channel`, `config`
JSON holding `{credential: {...}}`, `dialog_id`, `status`) +
`ChatChannelService` and RESTful CRUD under `/api/v1/chat_channels`.
- Channel framework under `api/channels/`: a `core` registry +
per-channel packages that self-register a builder and implement a common
`Channel` interface (`start`/`stop`/`send` + inbound normalization) over
`IncomingMessage`/`OutgoingMessage`.
- Embedded **reconcile loop** in `ragflow_server`
(`api/channels/bootstrap.py`): loads enabled bots, and
starts/stops/restarts them as rows change (no server restart needed).
Inbound messages run the connected dialog via the non-streaming
completion path, keeping per-end-user conversation history.
- Missing optional channel SDKs degrade gracefully (channel skipped with
a warning; others unaffected). Channel-level errors are logged, not
crashed.
- Feishu's WebSocket client runs in a dedicated thread with its own
event loop to avoid cross-loop/contextvars conflicts with the channel
runtime.
**Frontend**
- **Settings → Chat channels** panel: available-channels grid +
configured-bots list with add/edit/delete and a **Connect assistant**
popup that binds a bot to a dialog.
- Brand icons via simple-icons / reused shared data-source assets, with
colored fallbacks for brands not available.
- Route, sidebar entry, i18n (en/zh), and a top-nav segment-boundary fix
so the settings page no longer highlights the Chat tab.
### Type of change
- [x] New Feature (non-breaking change which adds functionality)
### Notes
- DB: new `chat_channel` table is auto-created; `chat_channel.dialog_id`
is also covered by a `migrate_db` `alter_db_add_column` for existing
installs.
- Channel SDKs (`lark-oapi`, `discord.py`, `python-telegram-bot`,
`line-bot-sdk`, `wechatpy`, `aiohttp`) added to dependencies.
- Screenshots / per-channel credential docs to follow.
<img width="1338" height="1290" alt="Image"
src="https://github.com/user-attachments/assets/042cb2f9-0dad-4e6a-bcf7-43ced4bbd704"
/>
<img width="1344" height="738" alt="Image"
src="https://github.com/user-attachments/assets/373cd08e-ec40-4c67-9c51-4d948b1ba617"
/>
<img width="672" height="887" alt="Image"
src="https://github.com/user-attachments/assets/5a34953f-a9a3-4c1e-869e-5eff0dc64c84"
/>
---------
2026-06-12 18:21:30 +08:00
|
|
|
|
- 2026-06-15 支援飛書、Discord、Telegram、Line 等多種聊天管道。
|
2026-04-30 20:12:29 +08:00
|
|
|
|
- 2026-04-24 支援 DeepSeek v4 版本。
|
2026-04-03 17:29:48 +08:00
|
|
|
|
- 2026-03-24 發布 [RAGFlow 官方 Skill](https://clawhub.ai/yingfeng/ragflow-skill) — 提供官方 Skill 以透過 OpenClaw 訪問 RAGFlow 數據集。
|
2025-12-27 20:44:35 +08:00
|
|
|
|
- 2025-12-26 支援AI代理的「記憶」功能。
|
|
|
|
|
|
- 2025-11-19 支援 Gemini 3 Pro。
|
2025-11-21 14:51:58 +08:00
|
|
|
|
- 2025-11-12 支援從 Confluence、S3、Notion、Discord、Google Drive 進行資料同步。
|
2025-10-27 12:20:23 +08:00
|
|
|
|
- 2025-10-23 支援 MinerU 和 Docling 作為文件解析方法。
|
2025-10-15 09:58:07 +08:00
|
|
|
|
- 2025-10-15 支援可編排的資料管道。
|
2025-08-08 11:54:40 +08:00
|
|
|
|
- 2025-08-08 支援 OpenAI 最新的 GPT-5 系列模型。
|
2025-12-27 20:44:35 +08:00
|
|
|
|
- 2025-08-01 支援 agentic workflow 和 MCP。
|
2025-05-28 18:31:50 +08:00
|
|
|
|
- 2025-05-23 為 Agent 新增 Python/JS 程式碼執行器元件。
|
2025-12-27 20:44:35 +08:00
|
|
|
|
- 2025-03-19 PDF和DOCX中的圖支持用多模態大模型去解析得到描述。
|
Feat: chat channels — connect assistants to external messaging bots (#15850)
### What problem does this PR solve?
#15844
Adds a **Chat channels** capability so a RAGFlow assistant (Dialog) can
be exposed as a bot on external messaging platforms (Feishu/Lark,
Discord, Telegram, Slack, WeCom, LINE, etc.). An admin configures a bot
in the UI, connects it to an assistant, and inbound messages are
answered from that assistant's knowledge base — replies are delivered
back on the channel.
**Feishu/Lark is implemented and tested end-to-end.** Discord, Telegram,
LINE, and WeCom are scaffolded against the same interface; the remaining
listed channels are tracked as follow-ups.
### Design
**Backend**
- New `chat_channel` table (`tenant_id`, `name`, `channel`, `config`
JSON holding `{credential: {...}}`, `dialog_id`, `status`) +
`ChatChannelService` and RESTful CRUD under `/api/v1/chat_channels`.
- Channel framework under `api/channels/`: a `core` registry +
per-channel packages that self-register a builder and implement a common
`Channel` interface (`start`/`stop`/`send` + inbound normalization) over
`IncomingMessage`/`OutgoingMessage`.
- Embedded **reconcile loop** in `ragflow_server`
(`api/channels/bootstrap.py`): loads enabled bots, and
starts/stops/restarts them as rows change (no server restart needed).
Inbound messages run the connected dialog via the non-streaming
completion path, keeping per-end-user conversation history.
- Missing optional channel SDKs degrade gracefully (channel skipped with
a warning; others unaffected). Channel-level errors are logged, not
crashed.
- Feishu's WebSocket client runs in a dedicated thread with its own
event loop to avoid cross-loop/contextvars conflicts with the channel
runtime.
**Frontend**
- **Settings → Chat channels** panel: available-channels grid +
configured-bots list with add/edit/delete and a **Connect assistant**
popup that binds a bot to a dialog.
- Brand icons via simple-icons / reused shared data-source assets, with
colored fallbacks for brands not available.
- Route, sidebar entry, i18n (en/zh), and a top-nav segment-boundary fix
so the settings page no longer highlights the Chat tab.
### Type of change
- [x] New Feature (non-breaking change which adds functionality)
### Notes
- DB: new `chat_channel` table is auto-created; `chat_channel.dialog_id`
is also covered by a `migrate_db` `alter_db_add_column` for existing
installs.
- Channel SDKs (`lark-oapi`, `discord.py`, `python-telegram-bot`,
`line-bot-sdk`, `wechatpy`, `aiohttp`) added to dependencies.
- Screenshots / per-channel credential docs to follow.
<img width="1338" height="1290" alt="Image"
src="https://github.com/user-attachments/assets/042cb2f9-0dad-4e6a-bcf7-43ced4bbd704"
/>
<img width="1344" height="738" alt="Image"
src="https://github.com/user-attachments/assets/373cd08e-ec40-4c67-9c51-4d948b1ba617"
/>
<img width="672" height="887" alt="Image"
src="https://github.com/user-attachments/assets/5a34953f-a9a3-4c1e-869e-5eff0dc64c84"
/>
---------
2026-06-12 18:21:30 +08:00
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
## 🎉 關注項目
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
|
|
|
|
|
⭐️ 點擊右上角的 Star 追蹤 RAGFlow，可以取得最新發布的即時通知 !🌟
|
|
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
<div align="center" style="margin-top:20px;margin-bottom:20px;">
|
|
|
|
|
|
<img src="https://github.com/user-attachments/assets/18c9707e-b8aa-4caf-a154-037089c105ba" width="1200"/>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
|
|
|
|
## 🌟 主要功能
|
|
|
|
|
|
|
|
|
|
|
|
### 🍭 **"Quality in, quality out"**
|
|
|
|
|
|
|
|
|
|
|
|
- 基於[深度文件理解](./deepdoc/README.md)，能夠從各類複雜格式的非結構化資料中提取真知灼見。
|
|
|
|
|
|
- 真正在無限上下文（token）的場景下快速完成大海撈針測試。
|
|
|
|
|
|
|
|
|
|
|
|
### 🍱 **基於模板的文字切片**
|
|
|
|
|
|
|
|
|
|
|
|
- 不只是智能，更重要的是可控可解釋。
|
|
|
|
|
|
- 多種文字範本可供選擇
|
|
|
|
|
|
|
|
|
|
|
|
### 🌱 **有理有據、最大程度降低幻覺（hallucination）**
|
|
|
|
|
|
|
|
|
|
|
|
- 文字切片過程視覺化，支援手動調整。
|
|
|
|
|
|
- 有理有據：答案提供關鍵引用的快照並支持追根溯源。
|
|
|
|
|
|
|
|
|
|
|
|
### 🍔 **相容各類異質資料來源**
|
|
|
|
|
|
|
2025-12-30 09:39:28 +08:00
|
|
|
|
- 支援豐富的文件類型，包括 Word 文件、PPT、excel 表格、txt 檔案、圖片、PDF、影印件、複印件、結構化資料、網頁等。
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
### 🛀 **全程無憂、自動化的 RAG 工作流程**
|
|
|
|
|
|
|
|
|
|
|
|
- 全面優化的 RAG 工作流程可以支援從個人應用乃至超大型企業的各類生態系統。
|
|
|
|
|
|
- 大語言模型 LLM 以及向量模型皆支援配置。
|
|
|
|
|
|
- 基於多路召回、融合重排序。
|
|
|
|
|
|
- 提供易用的 API，可輕鬆整合到各類企業系統。
|
|
|
|
|
|
|
|
|
|
|
|
## 🔎 系統架構
|
|
|
|
|
|
|
|
|
|
|
|
<div align="center" style="margin-top:20px;margin-bottom:20px;">
|
2025-10-16 14:30:55 +08:00
|
|
|
|
<img src="https://github.com/user-attachments/assets/31b0dd6f-ca4f-445a-9457-70cb44a381b2" width="1000"/>
|
2025-01-17 18:22:02 +08:00
|
|
|
|
</div>
|
|
|
|
|
|
|
2026-05-06 11:57:29 +08:00
|
|
|
|
## 🎬 自行架設
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
### 📝 前提條件
|
|
|
|
|
|
|
|
|
|
|
|
- CPU >= 4 核
|
|
|
|
|
|
- RAM >= 16 GB
|
|
|
|
|
|
- Disk >= 50 GB
|
|
|
|
|
|
- Docker >= 24.0.0 & Docker Compose >= v2.26.1
|
2026-05-25 20:23:30 +08:00
|
|
|
|
- Python >= 3.13
|
2025-05-16 16:28:21 +08:00
|
|
|
|
- [gVisor](https://gvisor.dev/docs/user_guide/install/): 僅在您打算使用 RAGFlow 的代碼執行器（沙箱）功能時才需要安裝。
|
|
|
|
|
|
|
|
|
|
|
|
> [!TIP]
|
|
|
|
|
|
> 如果你並沒有在本機安裝 Docker（Windows、Mac，或 Linux）, 可以參考文件 [Install Docker Engine](https://docs.docker.com/engine/install/) 自行安裝。
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
### 🚀 啟動伺服器
|
|
|
|
|
|
|
|
|
|
|
|
1. 確保 `vm.max_map_count` 不小於 262144：
|
|
|
|
|
|
|
|
|
|
|
|
> 如需確認 `vm.max_map_count` 的大小：
|
|
|
|
|
|
>
|
|
|
|
|
|
> ```bash
|
|
|
|
|
|
> $ sysctl vm.max_map_count
|
|
|
|
|
|
> ```
|
|
|
|
|
|
>
|
|
|
|
|
|
> 如果 `vm.max_map_count` 的值小於 262144，可以進行重設：
|
|
|
|
|
|
>
|
|
|
|
|
|
> ```bash
|
|
|
|
|
|
> # 這裡我們設為 262144:
|
|
|
|
|
|
> $ sudo sysctl -w vm.max_map_count=262144
|
|
|
|
|
|
> ```
|
|
|
|
|
|
>
|
|
|
|
|
|
> 你的改動會在下次系統重新啟動時被重置。如果希望做永久改動，還需要在 **/etc/sysctl.conf** 檔案裡把 `vm.max_map_count` 的值再相應更新一遍：
|
|
|
|
|
|
>
|
|
|
|
|
|
> ```bash
|
|
|
|
|
|
> vm.max_map_count=262144
|
|
|
|
|
|
> ```
|
2025-10-29 00:34:39 +08:00
|
|
|
|
>
|
2025-01-17 18:22:02 +08:00
|
|
|
|
2. 克隆倉庫：
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
$ git clone https://github.com/infiniflow/ragflow.git
|
|
|
|
|
|
```
|
|
|
|
|
|
3. 進入 **docker** 資料夾，利用事先編譯好的 Docker 映像啟動伺服器：
|
|
|
|
|
|
|
2025-03-04 19:21:28 +08:00
|
|
|
|
> [!CAUTION]
|
|
|
|
|
|
> 所有 Docker 映像檔都是為 x86 平台建置的。目前，我們不提供 ARM64 平台的 Docker 映像檔。
|
|
|
|
|
|
> 如果您使用的是 ARM64 平台，請使用 [這份指南](https://ragflow.io/docs/dev/build_docker_image) 來建置適合您系統的 Docker 映像檔。
|
|
|
|
|
|
|
2026-06-29 09:40:45 +08:00
|
|
|
|
> 執行以下指令會自動下載 RAGFlow Docker 映像 `v0.26.2`。請參考下表查看不同 Docker 發行版的說明。如需下載不同於 `v0.26.2` 的 Docker 映像，請在執行 `docker compose` 啟動服務之前先更新 **docker/.env** 檔案內的 `RAGFLOW_IMAGE` 變數。
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-10-29 00:34:39 +08:00
|
|
|
|
```bash
|
2025-02-19 13:19:36 +08:00
|
|
|
|
$ cd ragflow/docker
|
2025-12-31 20:07:40 +08:00
|
|
|
|
|
2026-06-29 09:40:45 +08:00
|
|
|
|
# git checkout v0.26.2
|
2025-11-19 19:40:55 +08:00
|
|
|
|
# 可選：使用穩定版標籤（查看發佈：https://github.com/infiniflow/ragflow/releases）
|
2025-11-13 09:50:47 +08:00
|
|
|
|
# 此步驟確保程式碼中的 entrypoint.sh 檔案與 Docker 映像版本一致。
|
2025-11-11 19:56:54 +08:00
|
|
|
|
|
2025-11-12 13:57:35 +08:00
|
|
|
|
# Use CPU for DeepDoc tasks:
|
2025-02-19 13:19:36 +08:00
|
|
|
|
$ docker compose -f docker-compose.yml up -d
|
2025-03-17 09:51:13 +08:00
|
|
|
|
|
2025-11-12 13:57:35 +08:00
|
|
|
|
# To use GPU to accelerate DeepDoc tasks:
|
2025-10-23 23:02:27 +08:00
|
|
|
|
# sed -i '1i DEVICE=gpu' .env
|
|
|
|
|
|
# docker compose -f docker-compose.yml up -d
|
2025-10-29 00:34:39 +08:00
|
|
|
|
```
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
2025-11-12 13:57:35 +08:00
|
|
|
|
> 注意：在 `v0.22.0` 之前的版本，我們會同時提供包含 embedding 模型的映像和不含 embedding 模型的 slim 映像。具體如下：
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
2025-12-17 19:27:47 +08:00
|
|
|
|
| RAGFlow image tag | Image size (GB) | Has embedding models? | Stable? |
|
|
|
|
|
|
|-------------------|-----------------|-----------------------|----------------|
|
|
|
|
|
|
| v0.21.1 | ≈9 | ✔️ | Stable release |
|
|
|
|
|
|
| v0.21.1-slim | ≈2 | ❌ | Stable release |
|
2025-11-12 13:57:35 +08:00
|
|
|
|
|
|
|
|
|
|
> 從 `v0.22.0` 開始，我們只發佈 slim 版本，並且不再在映像標籤後附加 **-slim** 後綴。
|
2025-10-27 11:31:56 +08:00
|
|
|
|
|
2025-10-29 00:34:39 +08:00
|
|
|
|
> [!TIP]
|
|
|
|
|
|
> 如果你遇到 Docker 映像檔拉不下來的問題，可以在 **docker/.env** 檔案內根據變數 `RAGFLOW_IMAGE` 的註解提示選擇華為雲或阿里雲的對應映像。
|
|
|
|
|
|
>
|
|
|
|
|
|
> - 華為雲鏡像名：`swr.cn-north-4.myhuaweicloud.com/infiniflow/ragflow`
|
2026-03-06 18:03:35 +08:00
|
|
|
|
> - 阿里雲鏡像名：`registry.cn-hangzhou.aliyuncs.com/infiniflow/ragflow`
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
4. 伺服器啟動成功後再次確認伺服器狀態：
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
2025-10-23 23:02:27 +08:00
|
|
|
|
$ docker logs -f docker-ragflow-cpu-1
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
_出現以下介面提示說明伺服器啟動成功：_
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
2025-01-21 00:22:29 -03:00
|
|
|
|
____ ___ ______ ______ __
|
2025-01-17 18:22:02 +08:00
|
|
|
|
/ __ \ / | / ____// ____// /____ _ __
|
|
|
|
|
|
/ /_/ // /| | / / __ / /_ / // __ \| | /| / /
|
2025-01-21 00:22:29 -03:00
|
|
|
|
/ _, _// ___ |/ /_/ // __/ / // /_/ /| |/ |/ /
|
|
|
|
|
|
/_/ |_|/_/ |_|\____//_/ /_/ \____/ |__/|__/
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
* Running on all addresses (0.0.0.0)
|
|
|
|
|
|
```
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-12-30 09:39:28 +08:00
|
|
|
|
> 如果您跳過這一步驟系統確認步驟就登入 RAGFlow，你的瀏覽器有可能會提示 `network abnormal` 或 `網路異常`，因為 RAGFlow 可能並未完全啟動成功。
|
2025-10-29 00:34:39 +08:00
|
|
|
|
>
|
2025-01-17 18:22:02 +08:00
|
|
|
|
5. 在你的瀏覽器中輸入你的伺服器對應的 IP 位址並登入 RAGFlow。
|
2025-10-29 00:34:39 +08:00
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
> 上面這個範例中，您只需輸入 http://IP_OF_YOUR_MACHINE 即可：未改動過設定則無需輸入連接埠（預設的 HTTP 服務連接埠 80）。
|
2025-10-29 00:34:39 +08:00
|
|
|
|
>
|
2025-01-17 18:22:02 +08:00
|
|
|
|
6. 在 [service_conf.yaml.template](./docker/service_conf.yaml.template) 檔案的 `user_default_llm` 欄位設定 LLM factory，並在 `API_KEY` 欄填入和你選擇的大模型相對應的 API key。
|
|
|
|
|
|
|
|
|
|
|
|
> 詳見 [llm_api_key_setup](https://ragflow.io/docs/dev/llm_api_key_setup)。
|
2025-10-29 00:34:39 +08:00
|
|
|
|
>
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
_好戲開始，接著奏樂接著舞！ _
|
|
|
|
|
|
|
|
|
|
|
|
## 🔧 系統配置
|
|
|
|
|
|
|
|
|
|
|
|
系統配置涉及以下三份文件：
|
|
|
|
|
|
|
2025-02-28 16:09:40 +08:00
|
|
|
|
- [.env](./docker/.env)：存放一些系統環境變量，例如 `SVR_HTTP_PORT`、`MYSQL_PASSWORD`、`MINIO_PASSWORD` 等。
|
2025-01-17 18:22:02 +08:00
|
|
|
|
- [service_conf.yaml.template](./docker/service_conf.yaml.template)：設定各類別後台服務。
|
|
|
|
|
|
- [docker-compose.yml](./docker/docker-compose.yml): 系統依賴該檔案完成啟動。
|
|
|
|
|
|
|
|
|
|
|
|
請務必確保 [.env](./docker/.env) 檔案中的變數設定與 [service_conf.yaml.template](./docker/service_conf.yaml.template) 檔案中的設定保持一致！
|
|
|
|
|
|
|
|
|
|
|
|
如果無法存取映像網站 hub.docker.com 或模型網站 huggingface.co，請依照 [.env](./docker/.env) 註解修改 `RAGFLOW_IMAGE` 和 `HF_ENDPOINT`。
|
|
|
|
|
|
|
|
|
|
|
|
> [./docker/README](./docker/README.md) 解釋了 [service_conf.yaml.template](./docker/service_conf.yaml.template) 用到的環境變數設定和服務配置。
|
|
|
|
|
|
|
2025-10-29 00:34:39 +08:00
|
|
|
|
如需更新預設的 HTTP 服務連接埠(80), 可以在[docker-compose.yml](./docker/docker-compose.yml) 檔案中將配置 `80:80` 改為 `<YOUR_SERVING_PORT>:80` 。
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
> 所有系統配置都需要透過系統重新啟動生效：
|
|
|
|
|
|
>
|
|
|
|
|
|
> ```bash
|
2025-02-19 13:19:36 +08:00
|
|
|
|
> $ docker compose -f docker-compose.yml up -d
|
2025-01-17 18:22:02 +08:00
|
|
|
|
> ```
|
|
|
|
|
|
|
|
|
|
|
|
###把文檔引擎從 Elasticsearch 切換成為 Infinity
|
|
|
|
|
|
|
|
|
|
|
|
RAGFlow 預設使用 Elasticsearch 儲存文字和向量資料. 如果要切換為 [Infinity](https://github.com/infiniflow/infinity/), 可以按照下面步驟進行:
|
|
|
|
|
|
|
|
|
|
|
|
1. 停止所有容器運作:
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
$ docker compose -f docker/docker-compose.yml down -v
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2025-10-29 00:34:39 +08:00
|
|
|
|
Note: `-v` 將會刪除 docker 容器的 volumes，已有的資料會被清空。
|
2025-01-17 18:22:02 +08:00
|
|
|
|
2. 設定 **docker/.env** 目錄中的 `DOC_ENGINE` 為 `infinity`.
|
|
|
|
|
|
3. 啟動容器:
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
2025-02-19 13:19:36 +08:00
|
|
|
|
$ docker compose -f docker-compose.yml up -d
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
> [!WARNING]
|
|
|
|
|
|
> Infinity 目前官方並未正式支援在 Linux/arm64 架構下的機器上運行.
|
|
|
|
|
|
|
2025-11-12 13:57:35 +08:00
|
|
|
|
## 🔧 原始碼編譯 Docker 映像
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
本 Docker 映像大小約 2 GB 左右並且依賴外部的大模型和 embedding 服務。
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
git clone https://github.com/infiniflow/ragflow.git
|
|
|
|
|
|
cd ragflow/
|
2025-10-23 23:02:27 +08:00
|
|
|
|
docker build --platform linux/amd64 -f Dockerfile -t infiniflow/ragflow:nightly .
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```
|
|
|
|
|
|
|
2025-12-29 17:43:55 +08:00
|
|
|
|
若您位於代理環境，可傳遞代理參數：
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
docker build --platform linux/amd64 \
|
|
|
|
|
|
--build-arg http_proxy=http://YOUR_PROXY:PORT \
|
|
|
|
|
|
--build-arg https_proxy=http://YOUR_PROXY:PORT \
|
|
|
|
|
|
-f Dockerfile -t infiniflow/ragflow:nightly .
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
## 🔨 以原始碼啟動服務
|
|
|
|
|
|
|
2025-08-28 09:53:16 +08:00
|
|
|
|
1. 安裝 `uv` 和 `pre-commit`。如已安裝，可跳過此步驟：
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```bash
|
2025-04-24 00:25:33 -03:00
|
|
|
|
pipx install uv pre-commit
|
2025-02-24 20:15:40 +08:00
|
|
|
|
export UV_INDEX=https://mirrors.aliyun.com/pypi/simple
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```
|
|
|
|
|
|
2. 下載原始碼並安裝 Python 依賴：
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
git clone https://github.com/infiniflow/ragflow.git
|
|
|
|
|
|
cd ragflow/
|
2026-05-21 19:09:19 +08:00
|
|
|
|
uv sync --python 3.13 # install RAGFlow dependent python modules
|
feat(agent): align Go agent behavior with Python (except retrieval component) (#16225)
## Summary
Aligns the **Go agent runtime/canvas/components/tools** behavior with
the **Python `agent/` implementation** so the same stored canvas DSL
produces the same execution result on either side. Every component,
tool, and runtime primitive in `internal/agent/` is now driven by the
same semantics as its Python counterpart — variable resolution, template
substitution, control flow, error reporting, retry/cancel, and stream
event shapes.
The **retrieval component is the one explicit exception** in this PR. It
is being reworked in a separate change and is excluded from this
alignment pass; the wrapper slot (`universe_a_wrappers.go →
newRetrievalComponent`) is preserved.
## Scope of alignment
### Components (all aligned with `agent/component/`)
`Begin` · `Message` · `LLM` (incl. ChatTemplateKwargs,
MessageHistoryWindowSize, VisualFiles, Cite, OutputStructure,
JSONOutput, TopP, MaxRetries, DelayAfterError, credentials) · `Agent`
(react + tool artifact capture + `Reset()` interface-assert) · `Switch`
(12/12 operators, Python-equivalent semantics) · `Categorize` · `Invoke`
· `Iteration` · `Loop` (macro-expansion through `workflowx.AddLoopNode`)
· `UserFillUp` (Python-equivalent interrupt/resume via eino
`compose.Interrupt`/`ResumeWithData`) · `FillUp` · `DataOperations` ·
`ListOperations` · `StringTransform` · `VariableAggregator` ·
`VariableAssigner` · `Browser` (full stagehand runtime parity) ·
`DocsGenerator` · `ExcelProcessor`.
### Tools (all aligned with `agent/tools/`)
`Retrieval` (wrapper slot only — logic out of scope) · `MCPToolAdapter`
(streamable-HTTP) · `CodeExec` (sandbox bridge with
`code_exec_contract.go` matching Python contract) · `AkShare` · `ArXiv`
· `Crawler` · `DeepL` · `DuckDuckGo` · `Email` · `ExeSQL` · `GitHub` ·
`Google` · `GoogleScholar` · `Jin10` · `PubMed` · `QWeather` · `SearXNG`
· `Tavily` · `Tushare` · `Wencai` · `Wikipedia` · `YahooFinance` —
uniform `eino tool.InvokableTool` interface, SSRF protection, shared
HTTP client.
### Canvas execution engine (`internal/agent/canvas/`)
Aligned with Python's `agent/canvas.py`:
- **Scheduler** (`scheduler.go`): state pre/post handlers, node lambdas,
per-component timeout resolver (4-level: per-class env → per-class table
→ uniform env → 600s fallback), `legacyNoOpNames`.
- **Loop subgraph** (`loop_subgraph.go`): Python-equivalent
`AddLoopNode` macro expansion + condition translation.
- **Multibranch** (`multibranch.go`): `Switch` / `Categorize` routing
via `compose.NewGraphMultiBranch` — same branch selection semantics as
Python.
- **Parallel subgraph** (`parallel_subgraph.go`): matches Python's
parallel fan-out contract.
- **Interrupt/Resume** (`interrupt_resume.go`): `UserFillUpNodeBody` /
`IsInterruptError` / `ExtractInterruptContexts` — replaces the
deprecated Python sentinel chain with eino's native interrupt API,
preserving the same external behavior.
- **Checkpoint** (`checkpoint_store.go`): `RedisCheckPointStore`
Get/Set/Delete, with business metadata (status / canvas_id /
parent_run_id) on a parallel Redis Hash.
- **RunTracker** (`run_tracker.go`): Start / MarkSucceeded / MarkFailed
/ MarkCancelled / AttachCheckpoint — same lifecycle as the Python run
record.
- **Cancel** (`cancel.go`): Redis pub/sub watch.
- **Stream** (`stream.go`): SSE channel with `messages` / `waiting` /
`errors` / `done` events, same shape as Python's `agent.canvas.RunEvent`
payload.
### DSL bridge (`internal/agent/dsl/`)
- `normalize.go`: v1↔v2 collapsed into a single wire format — Python and
Go consume the same stored JSON.
- `reset.go`: per-run state reset matches Python's `Canvas.reset()`
semantics.
- Testdata mirrors Python's `agent_msg.json` / `all.json` / etc.
### Runtime (`internal/agent/runtime/`)
- `CanvasState` / `NewCanvasState` / `GetVar` / `SetVar` / `ReadVars`:
same `{{cpn_id@param}}` resolution model.
- `ResolveTemplate` (regex fast path + gonja fallback) — Python
Jinja-style semantics.
- `selector.go`, `metrics.go`, `component.go`: shared runtime contracts.
## Out of scope (intentionally)
- **`Retrieval` component logic** — wrapped only; full parity lands in a
follow-up PR.
- **Frontend** — only minor dsl-bridge / canvas UX fixes ride along.
- **CLI / admin / model registry** — orthogonal to agent behavior.
## How alignment is verified
`internal/service/agent_run_e2e_test.go` exercises the **full production
chain** against real Python-shaped DSL fixtures:
```
loadCanvasForUser → versionDAO.GetLatest → decodeCanvasFromDSL →
canvas.Compile → cc.Workflow.Invoke → answer extraction
```
using in-memory SQLite + miniredis (no Docker). Covers:
- `TestRunAgent_RealCanvas_BeginMessage` — happy path, `{{sys.query}}`
resolution
- `TestRunAgent_RealCanvas_WaitForUserResume` — two-run resume cycle
(Python-equivalent)
- `TestRunAgent_RealCanvas_CompileFails` — unknown component name →
sanitized error (Python-equivalent)
- `TestRunAgent_RealCanvas_InvokeFails` — unresolvable template ref
(Python-equivalent)
- `TestRunAgent_RunTracker_AttachCheckpoint_CallSequence` —
Start→AttachCheckpoint→MarkSucceeded lifecycle
`internal/handler/agent_test.go` — SSE streaming parity (`Content-Type:
text/event-stream`, `data: {…}\n\n`, trailing `data: [DONE]\n\n`,
OpenAI-compatible non-stream `choices`).
`internal/agent/canvas/fixture_compile_test.go` + per-component tests
pin the Python-equivalent outputs.
```
go test -count=1 -v -run 'TestRunAgent_RealCanvas|TestRunAgent_RunTracker' ./internal/service/
```
## Design reference
`docs/develop/agent-go-port-design.md` (1329 lines, last cross-checked
2026-06-17) — module layout, per-component / per-tool inventory,
corner-case catalogue, and the actionable backlog (Section 14, including
the retrieval alignment follow-up).
---------
Co-authored-by: Claude <noreply@anthropic.com>
2026-06-22 11:58:29 +08:00
|
|
|
|
uv run python3 ragflow_deps/download_deps.py
|
2025-04-24 00:25:33 -03:00
|
|
|
|
pre-commit install
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```
|
|
|
|
|
|
3. 透過 Docker Compose 啟動依賴的服務（MinIO, Elasticsearch, Redis, and MySQL）：
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
docker compose -f docker/docker-compose-base.yml up -d
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
在 `/etc/hosts` 中加入以下程式碼，將 **conf/service_conf.yaml** 檔案中的所有 host 位址都解析為 `127.0.0.1`：
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```
|
2025-05-16 11:14:57 +08:00
|
|
|
|
127.0.0.1 es01 infinity mysql minio redis sandbox-executor-manager
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```
|
2025-01-21 00:22:29 -03:00
|
|
|
|
4. 如果無法存取 HuggingFace，可以把環境變數 `HF_ENDPOINT` 設為對應的鏡像網站：
|
|
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
export HF_ENDPOINT=https://hf-mirror.com
|
|
|
|
|
|
```
|
2025-05-14 15:44:24 +08:00
|
|
|
|
5. 如果你的操作系统没有 jemalloc，请按照如下方式安装：
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-05-14 15:44:24 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
# ubuntu
|
|
|
|
|
|
sudo apt-get install libjemalloc-dev
|
|
|
|
|
|
# centos
|
|
|
|
|
|
sudo yum install jemalloc
|
2025-09-03 10:50:39 +08:00
|
|
|
|
# mac
|
|
|
|
|
|
sudo brew install jemalloc
|
2025-05-14 15:44:24 +08:00
|
|
|
|
```
|
|
|
|
|
|
6. 啟動後端服務：
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-05-14 15:44:24 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
source .venv/bin/activate
|
|
|
|
|
|
export PYTHONPATH=$(pwd)
|
|
|
|
|
|
bash docker/launch_backend_service.sh
|
|
|
|
|
|
```
|
|
|
|
|
|
7. 安裝前端依賴：
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-05-14 15:44:24 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
cd web
|
|
|
|
|
|
npm install
|
|
|
|
|
|
```
|
|
|
|
|
|
8. 啟動前端服務：
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
npm run dev
|
2025-01-17 18:22:02 +08:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
以下界面說明系統已成功啟動：_
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-10-29 00:34:39 +08:00
|
|
|
|
|
2025-01-21 00:22:29 -03:00
|
|
|
|
```
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
2025-10-29 00:34:39 +08:00
|
|
|
|
```
|
2025-05-14 15:44:24 +08:00
|
|
|
|
9. 開發完成後停止 RAGFlow 前端和後端服務：
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
pkill -f "ragflow_server.py|task_executor.py"
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2025-01-17 18:22:02 +08:00
|
|
|
|
## 📚 技術文檔
|
|
|
|
|
|
|
|
|
|
|
|
- [Quickstart](https://ragflow.io/docs/dev/)
|
2025-03-18 19:49:06 +08:00
|
|
|
|
- [Configuration](https://ragflow.io/docs/dev/configurations)
|
|
|
|
|
|
- [Release notes](https://ragflow.io/docs/dev/release_notes)
|
2026-03-16 07:53:52 +05:30
|
|
|
|
- [User guides](https://ragflow.io/docs/category/user-guides)
|
|
|
|
|
|
- [Developer guides](https://ragflow.io/docs/category/developer-guides)
|
2025-01-17 18:22:02 +08:00
|
|
|
|
- [References](https://ragflow.io/docs/dev/category/references)
|
2025-03-18 19:49:06 +08:00
|
|
|
|
- [FAQs](https://ragflow.io/docs/dev/faq)
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
## 📜 路線圖
|
|
|
|
|
|
|
2025-12-31 12:49:42 +08:00
|
|
|
|
詳見 [RAGFlow Roadmap 2026](https://github.com/infiniflow/ragflow/issues/12241) 。
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
## 🏄 開源社群
|
|
|
|
|
|
|
2026-05-09 11:28:44 +08:00
|
|
|
|
- [Discord](https://discord.gg/NjYzJD3GM3)
|
|
|
|
|
|
- [X](https://x.com/infiniflowai)
|
2025-01-17 18:22:02 +08:00
|
|
|
|
- [GitHub Discussions](https://github.com/orgs/infiniflow/discussions)
|
|
|
|
|
|
|
|
|
|
|
|
## 🙌 貢獻指南
|
|
|
|
|
|
|
2025-05-16 16:28:21 +08:00
|
|
|
|
RAGFlow 只有透過開源協作才能蓬勃發展。秉持這項精神,我們歡迎來自社區的各種貢獻。如果您有意參與其中,請查閱我們的 [貢獻者指南](https://ragflow.io/docs/dev/contributing) 。
|
2025-01-17 18:22:02 +08:00
|
|
|
|
|
|
|
|
|
|
## 🤝 商務合作
|
|
|
|
|
|
|
|
|
|
|
|
- [預約諮詢](https://aao615odquw.feishu.cn/share/base/form/shrcnjw7QleretCLqh1nuPo1xxh)
|
|
|
|
|
|
|
|
|
|
|
|
## 👥 加入社區
|
|
|
|
|
|
|
|
|
|
|
|
掃二維碼加入 RAGFlow 小助手，進 RAGFlow 交流群。
|
|
|
|
|
|
|
|
|
|
|
|
<p align="center">
|
|
|
|
|
|
<img src="https://github.com/infiniflow/ragflow/assets/7248/bccf284f-46f2-4445-9809-8f1030fb7585" width=50% height=50%>
|
|
|
|
|
|
</p>
|