2024-03-31 23:08:41 +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">
|
2024-03-31 23:08:41 +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>
|
2025-06-17 18:01:56 +08:00
|
|
|
|
<a href="./README_zh.md"><img alt="简体中文版自述文件" src="https://img.shields.io/badge/简体中文-DBEDFA"></a>
|
2025-06-16 21:14:50 +08:00
|
|
|
|
<a href="./README_tzh.md"><img alt="繁體版中文自述文件" src="https://img.shields.io/badge/繁體中文-DFE0E5"></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>
|
2024-03-31 23:08:41 +08:00
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
|
|
<p align="center">
|
2024-10-29 21:05:38 +08:00
|
|
|
|
<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)">
|
2024-04-25 14:31:54 +08:00
|
|
|
|
</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">
|
2024-10-29 21:05:38 +08:00
|
|
|
|
</a>
|
2024-03-31 23:08:41 +08:00
|
|
|
|
<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">
|
2024-10-29 21:05:38 +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>
|
2024-05-30 18:00:02 +08:00
|
|
|
|
<a href="https://github.com/infiniflow/ragflow/blob/main/LICENSE">
|
2024-10-29 21:05:38 +08:00
|
|
|
|
<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>
|
2024-03-31 23:08:41 +08:00
|
|
|
|
</p>
|
|
|
|
|
|
|
2024-06-01 16:24:10 +08:00
|
|
|
|
<h4 align="center">
|
2026-05-06 11:57:29 +08:00
|
|
|
|
<a href="https://cloud.ragflow.io">Cloud</a> |
|
2024-06-01 16:24:10 +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>
|
2024-06-01 16:24:10 +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>
|
|
|
|
|
|
|
2024-03-31 23:08:41 +08:00
|
|
|
|
## 💡 RAGFlow 是什么?
|
|
|
|
|
|
|
2025-12-31 20:07:40 +08:00
|
|
|
|
[RAGFlow](https://ragflow.io/) 是一款领先的开源检索增强生成([RAG](https://ragflow.io/basics/what-is-rag))引擎,通过融合前沿的 RAG 技术与 Agent 能力,为大型语言模型提供卓越的上下文层。它提供可适配任意规模企业的端到端 RAG 工作流,凭借融合式[上下文引擎](https://ragflow.io/basics/what-is-agent-context-engine)与预置的 Agent 模板,助力开发者以极致效率与精度将复杂数据转化为高可信、生产级的人工智能系统。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
2026-05-06 11:57:29 +08:00
|
|
|
|
## 🎮 快速开始
|
2024-05-27 14:01:52 +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
|
|
|
|
|
2024-06-07 19:01:09 +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"/>
|
2024-06-07 19:01:09 +08:00
|
|
|
|
</div>
|
|
|
|
|
|
|
2024-07-18 11:20:15 +08:00
|
|
|
|
## 🔥 近期更新
|
2024-05-12 13:40:47 +08:00
|
|
|
|
|
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 数据集。
|
2026-04-30 20:12:29 +08:00
|
|
|
|
- 2025-12-26 支持 AI 代理的"记忆"功能。
|
2025-12-27 20:44:35 +08:00
|
|
|
|
- 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 支持 OpenAI 最新的 GPT-5 系列模型。
|
2025-08-05 20:27:43 +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
|
|
|
|
|
2024-09-30 16:21:56 +08:00
|
|
|
|
|
|
|
|
|
|
## 🎉 关注项目
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
|
|
|
|
|
⭐️ 点击右上角的 Star 关注 RAGFlow,可以获取最新发布的实时通知 !🌟
|
|
|
|
|
|
|
2024-09-30 16:21:56 +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>
|
|
|
|
|
|
|
2024-03-31 23:08:41 +08:00
|
|
|
|
## 🌟 主要功能
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
2024-03-31 23:08:41 +08:00
|
|
|
|
### 🍭 **"Quality in, quality out"**
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
2024-04-01 14:01:21 +08:00
|
|
|
|
- 基于[深度文档理解](./deepdoc/README.md),能够从各类复杂格式的非结构化数据中提取真知灼见。
|
2024-04-01 10:54:11 +08:00
|
|
|
|
- 真正在无限上下文(token)的场景下快速完成大海捞针测试。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
### 🍱 **基于模板的文本切片**
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
|
|
|
|
|
- 不仅仅是智能,更重要的是可控可解释。
|
|
|
|
|
|
- 多种文本模板可供选择
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
### 🌱 **有理有据、最大程度降低幻觉(hallucination)**
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
|
|
|
|
|
- 文本切片过程可视化,支持手动调整。
|
|
|
|
|
|
- 有理有据:答案提供关键引用的快照并支持追根溯源。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
2024-03-31 23:12:25 +08:00
|
|
|
|
### 🍔 **兼容各类异构数据源**
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
2024-05-31 09:44:59 +01:00
|
|
|
|
- 支持丰富的文件类型,包括 Word 文档、PPT、excel 表格、txt 文件、图片、PDF、影印件、复印件、结构化数据、网页等。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
### 🛀 **全程无忧、自动化的 RAG 工作流**
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
|
|
|
|
|
- 全面优化的 RAG 工作流可以支持从个人应用乃至超大型企业的各类生态系统。
|
|
|
|
|
|
- 大语言模型 LLM 以及向量模型均支持配置。
|
|
|
|
|
|
- 基于多路召回、融合重排序。
|
|
|
|
|
|
- 提供易用的 API,可以轻松集成到各类企业系统。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
## 🔎 系统架构
|
|
|
|
|
|
|
|
|
|
|
|
<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"/>
|
2024-03-31 23:08:41 +08:00
|
|
|
|
</div>
|
|
|
|
|
|
|
2026-05-06 11:57:29 +08:00
|
|
|
|
## 🎬 自主托管
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
### 📝 前提条件
|
|
|
|
|
|
|
2024-04-19 18:02:53 +08:00
|
|
|
|
- CPU >= 4 核
|
2024-04-24 19:22:00 +08:00
|
|
|
|
- RAM >= 16 GB
|
2024-04-25 14:00:48 +08:00
|
|
|
|
- Disk >= 50 GB
|
2024-04-11 10:13:43 +08:00
|
|
|
|
- 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/) 自行安装。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
### 🚀 启动服务器
|
|
|
|
|
|
|
2024-06-03 17:01:02 +08:00
|
|
|
|
1. 确保 `vm.max_map_count` 不小于 262144:
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
> 如需确认 `vm.max_map_count` 的大小:
|
|
|
|
|
|
>
|
2024-04-01 10:54:11 +08:00
|
|
|
|
> ```bash
|
2024-03-31 23:08:41 +08:00
|
|
|
|
> $ sysctl vm.max_map_count
|
|
|
|
|
|
> ```
|
|
|
|
|
|
>
|
2024-04-07 09:41:53 +08:00
|
|
|
|
> 如果 `vm.max_map_count` 的值小于 262144,可以进行重置:
|
2024-03-31 23:08:41 +08:00
|
|
|
|
>
|
|
|
|
|
|
> ```bash
|
|
|
|
|
|
> # 这里我们设为 262144:
|
|
|
|
|
|
> $ sudo sysctl -w vm.max_map_count=262144
|
|
|
|
|
|
> ```
|
|
|
|
|
|
>
|
|
|
|
|
|
> 你的改动会在下次系统重启时被重置。如果希望做永久改动,还需要在 **/etc/sysctl.conf** 文件里把 `vm.max_map_count` 的值再相应更新一遍:
|
|
|
|
|
|
>
|
|
|
|
|
|
> ```bash
|
|
|
|
|
|
> vm.max_map_count=262144
|
|
|
|
|
|
> ```
|
|
|
|
|
|
|
|
|
|
|
|
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` 变量。
|
2024-10-10 19:24:54 +08:00
|
|
|
|
|
2024-03-31 23:08:41 +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 11:06:08 +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 11:06:08 +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
|
2024-03-31 23:08:41 +08:00
|
|
|
|
```
|
2025-12-31 20:07:40 +08:00
|
|
|
|
|
2025-11-12 13:57:35 +08:00
|
|
|
|
> 注意:在 `v0.22.0` 之前的版本,我们会同时提供包含 embedding 模型的镜像和不含 embedding 模型的 slim 镜像。具体如下:
|
2025-11-12 11:06:08 +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
|
|
|
|
|
2025-11-12 11:06:08 +08:00
|
|
|
|
> 从 `v0.22.0` 开始,我们只发布 slim 版本,并且不再在镜像标签后附加 **-slim** 后缀。
|
2025-10-27 11:31:56 +08:00
|
|
|
|
|
2025-01-21 00:22:29 -03:00
|
|
|
|
> [!TIP]
|
2024-12-13 18:57:22 +08:00
|
|
|
|
> 如果你遇到 Docker 镜像拉不下来的问题,可以在 **docker/.env** 文件内根据变量 `RAGFLOW_IMAGE` 的注释提示选择华为云或者阿里云的相应镜像。
|
2025-01-21 00:22:29 -03:00
|
|
|
|
>
|
2024-12-13 18:57:22 +08:00
|
|
|
|
> - 华为云镜像名:`swr.cn-north-4.myhuaweicloud.com/infiniflow/ragflow`
|
2026-03-06 18:03:35 +08:00
|
|
|
|
> - 阿里云镜像名:`registry.cn-hangzhou.aliyuncs.com/infiniflow/ragflow`
|
2024-12-13 18:57:22 +08:00
|
|
|
|
|
2024-03-31 23:08:41 +08:00
|
|
|
|
4. 服务器启动成功后再次确认服务器状态:
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
2024-03-31 23:08:41 +08:00
|
|
|
|
```bash
|
2025-10-23 23:02:27 +08:00
|
|
|
|
$ docker logs -f docker-ragflow-cpu-1
|
2024-03-31 23:08:41 +08:00
|
|
|
|
```
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
|
|
|
|
|
_出现以下界面提示说明服务器启动成功:_
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
```bash
|
2025-01-21 00:22:29 -03:00
|
|
|
|
____ ___ ______ ______ __
|
2024-09-29 16:28:07 +08:00
|
|
|
|
/ __ \ / | / ____// ____// /____ _ __
|
|
|
|
|
|
/ /_/ // /| | / / __ / /_ / // __ \| | /| / /
|
2025-01-21 00:22:29 -03:00
|
|
|
|
/ _, _// ___ |/ /_/ // __/ / // /_/ /| |/ |/ /
|
|
|
|
|
|
/_/ |_|/_/ |_|\____//_/ /_/ \____/ |__/|__/
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
2024-03-31 23:08:41 +08:00
|
|
|
|
* Running on all addresses (0.0.0.0)
|
2024-04-01 10:54:11 +08:00
|
|
|
|
```
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2025-12-30 09:39:28 +08:00
|
|
|
|
> 如果您在没有看到上面的提示信息出来之前,就尝试登录 RAGFlow,你的浏览器有可能会提示 `network abnormal` 或 `网络异常`。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
2024-04-08 19:20:57 +08:00
|
|
|
|
5. 在你的浏览器中输入你的服务器对应的 IP 地址并登录 RAGFlow。
|
|
|
|
|
|
> 上面这个例子中,您只需输入 http://IP_OF_YOUR_MACHINE 即可:未改动过配置则无需输入端口(默认的 HTTP 服务端口 80)。
|
2024-12-10 10:19:50 +08:00
|
|
|
|
6. 在 [service_conf.yaml.template](./docker/service_conf.yaml.template) 文件的 `user_default_llm` 栏配置 LLM factory,并在 `API_KEY` 栏填写和你选择的大模型相对应的 API key。
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
2024-06-01 16:24:10 +08:00
|
|
|
|
> 详见 [llm_api_key_setup](https://ragflow.io/docs/dev/llm_api_key_setup)。
|
2024-04-01 10:54:11 +08:00
|
|
|
|
|
|
|
|
|
|
_好戏开始,接着奏乐接着舞!_
|
|
|
|
|
|
|
2024-03-31 23:08:41 +08:00
|
|
|
|
## 🔧 系统配置
|
|
|
|
|
|
|
|
|
|
|
|
系统配置涉及以下三份文件:
|
|
|
|
|
|
|
|
|
|
|
|
- [.env](./docker/.env):存放一些基本的系统环境变量,比如 `SVR_HTTP_PORT`、`MYSQL_PASSWORD`、`MINIO_PASSWORD` 等。
|
2024-12-10 10:19:50 +08:00
|
|
|
|
- [service_conf.yaml.template](./docker/service_conf.yaml.template):配置各类后台服务。
|
2024-09-29 18:24:24 +08:00
|
|
|
|
- [docker-compose.yml](./docker/docker-compose.yml): 系统依赖该文件完成启动。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
2024-12-10 10:19:50 +08:00
|
|
|
|
请务必确保 [.env](./docker/.env) 文件中的变量设置与 [service_conf.yaml.template](./docker/service_conf.yaml.template) 文件中的配置保持一致!
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
2024-12-10 12:11:39 +08:00
|
|
|
|
如果不能访问镜像站点 hub.docker.com 或者模型站点 huggingface.co,请按照 [.env](./docker/.env) 注释修改 `RAGFLOW_IMAGE` 和 `HF_ENDPOINT`。
|
2024-09-29 18:24:24 +08:00
|
|
|
|
|
2024-12-10 12:11:39 +08:00
|
|
|
|
> [./docker/README](./docker/README.md) 解释了 [service_conf.yaml.template](./docker/service_conf.yaml.template) 用到的环境变量设置和服务配置。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
2024-09-29 18:24:24 +08:00
|
|
|
|
如需更新默认的 HTTP 服务端口(80), 可以在 [docker-compose.yml](./docker/docker-compose.yml) 文件中将配置 `80:80` 改为 `<YOUR_SERVING_PORT>:80`。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
> 所有系统配置都需要通过系统重启生效:
|
2024-04-01 10:54:11 +08:00
|
|
|
|
>
|
2024-03-31 23:08:41 +08:00
|
|
|
|
> ```bash
|
2025-02-19 13:19:36 +08:00
|
|
|
|
> $ docker compose -f docker-compose.yml up -d
|
2024-03-31 23:08:41 +08:00
|
|
|
|
> ```
|
|
|
|
|
|
|
2024-11-19 12:31:20 +08:00
|
|
|
|
### 把文档引擎从 Elasticsearch 切换成为 Infinity
|
2024-11-19 11:31:11 +08:00
|
|
|
|
|
|
|
|
|
|
RAGFlow 默认使用 Elasticsearch 存储文本和向量数据. 如果要切换为 [Infinity](https://github.com/infiniflow/infinity/), 可以按照下面步骤进行:
|
|
|
|
|
|
|
|
|
|
|
|
1. 停止所有容器运行:
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
$ docker compose -f docker/docker-compose.yml down -v
|
|
|
|
|
|
```
|
2025-02-19 16:51:33 +08:00
|
|
|
|
Note: `-v` 将会删除 docker 容器的 volumes,已有的数据会被清空。
|
2024-11-19 11:31:11 +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
|
2024-11-19 11:31:11 +08:00
|
|
|
|
```
|
|
|
|
|
|
|
2025-01-21 00:22:29 -03:00
|
|
|
|
> [!WARNING]
|
2024-11-19 11:31:11 +08:00
|
|
|
|
> Infinity 目前官方并未正式支持在 Linux/arm64 架构下的机器上运行.
|
|
|
|
|
|
|
2025-11-12 11:06:08 +08:00
|
|
|
|
## 🔧 源码编译 Docker 镜像
|
2024-09-29 17:27:15 +08:00
|
|
|
|
|
2024-12-09 12:44:57 +08:00
|
|
|
|
本 Docker 镜像大小约 2 GB 左右并且依赖外部的大模型和 embedding 服务。
|
2024-09-29 17:27:15 +08:00
|
|
|
|
|
|
|
|
|
|
```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 .
|
2024-09-29 17:27:15 +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 .
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2024-09-29 17:27:15 +08:00
|
|
|
|
## 🔨 以源代码启动服务
|
|
|
|
|
|
|
2025-08-28 09:53:16 +08:00
|
|
|
|
1. 安装 `uv` 和 `pre-commit`。如已经安装,可跳过本步骤:
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2024-09-29 17:27:15 +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
|
2024-09-29 17:27:15 +08:00
|
|
|
|
```
|
|
|
|
|
|
|
2025-01-21 00:22:29 -03:00
|
|
|
|
2. 下载源代码并安装 Python 依赖:
|
|
|
|
|
|
|
2024-09-29 17:27:15 +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
|
2024-09-29 17:27:15 +08:00
|
|
|
|
```
|
|
|
|
|
|
|
2025-01-21 00:22:29 -03:00
|
|
|
|
3. 通过 Docker Compose 启动依赖的服务(MinIO, Elasticsearch, Redis, and MySQL):
|
|
|
|
|
|
|
2024-09-29 17:27:15 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
docker compose -f docker/docker-compose-base.yml up -d
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2025-04-03 22:12:49 +08:00
|
|
|
|
在 `/etc/hosts` 中添加以下代码,目的是将 **conf/service_conf.yaml** 文件中的所有 host 地址都解析为 `127.0.0.1`:
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2024-09-29 17:27:15 +08:00
|
|
|
|
```
|
2025-05-16 11:14:57 +08:00
|
|
|
|
127.0.0.1 es01 infinity mysql minio redis sandbox-executor-manager
|
2025-01-21 00:22:29 -03:00
|
|
|
|
```
|
|
|
|
|
|
4. 如果无法访问 HuggingFace,可以把环境变量 `HF_ENDPOINT` 设成相应的镜像站点:
|
2024-09-29 17:27:15 +08:00
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
export HF_ENDPOINT=https://hf-mirror.com
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2025-05-14 15:44:24 +08:00
|
|
|
|
5. 如果你的操作系统没有 jemalloc,请按照如下方式安装:
|
|
|
|
|
|
|
|
|
|
|
|
```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
|
|
|
|
|
2024-09-29 17:27:15 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
source .venv/bin/activate
|
|
|
|
|
|
export PYTHONPATH=$(pwd)
|
|
|
|
|
|
bash docker/launch_backend_service.sh
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2025-05-14 15:44:24 +08:00
|
|
|
|
7. 安装前端依赖:
|
|
|
|
|
|
|
2024-09-29 17:27:15 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
cd web
|
2024-12-30 18:19:58 +08:00
|
|
|
|
npm install
|
2025-01-21 00:22:29 -03:00
|
|
|
|
```
|
2025-05-14 15:44:24 +08:00
|
|
|
|
|
|
|
|
|
|
8. 启动前端服务:
|
2025-01-21 00:22:29 -03:00
|
|
|
|
|
2024-09-29 17:27:15 +08:00
|
|
|
|
```bash
|
2025-01-21 00:22:29 -03:00
|
|
|
|
npm run dev
|
|
|
|
|
|
```
|
2024-09-29 17:27:15 +08:00
|
|
|
|
|
2025-01-21 00:22:29 -03:00
|
|
|
|
_以下界面说明系统已经成功启动:_
|
2024-09-29 17:27:15 +08:00
|
|
|
|
|
|
|
|
|
|

|
2025-05-14 15:44:24 +08:00
|
|
|
|
|
|
|
|
|
|
9. 开发完成后停止 RAGFlow 前端和后端服务:
|
|
|
|
|
|
|
2025-04-03 22:12:49 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
pkill -f "ragflow_server.py|task_executor.py"
|
|
|
|
|
|
```
|
2025-04-07 12:18:43 +08:00
|
|
|
|
|
2025-05-14 15:44:24 +08:00
|
|
|
|
|
2024-04-15 17:01:18 +08:00
|
|
|
|
## 📚 技术文档
|
2024-04-08 19:20:57 +08:00
|
|
|
|
|
2024-06-01 16:24:10 +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)
|
2024-06-07 09:06:46 +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)
|
2024-04-08 19:20:57 +08:00
|
|
|
|
|
2024-03-31 23:08:41 +08:00
|
|
|
|
## 📜 路线图
|
|
|
|
|
|
|
2025-12-31 12:49:42 +08:00
|
|
|
|
详见 [RAGFlow Roadmap 2026](https://github.com/infiniflow/ragflow/issues/12241) 。
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
## 🏄 开源社区
|
|
|
|
|
|
|
2026-05-09 11:28:44 +08:00
|
|
|
|
- [Discord](https://discord.gg/NjYzJD3GM3)
|
|
|
|
|
|
- [X](https://x.com/infiniflowai)
|
2024-06-01 16:24:10 +08:00
|
|
|
|
- [GitHub Discussions](https://github.com/orgs/infiniflow/discussions)
|
2024-03-31 23:08:41 +08:00
|
|
|
|
|
|
|
|
|
|
## 🙌 贡献指南
|
|
|
|
|
|
|
2025-05-16 16:28:21 +08:00
|
|
|
|
RAGFlow 只有通过开源协作才能蓬勃发展。秉持这一精神,我们欢迎来自社区的各种贡献。如果您有意参与其中,请查阅我们的 [贡献者指南](https://ragflow.io/docs/dev/contributing) 。
|
2024-04-01 13:51:41 +08:00
|
|
|
|
|
2024-07-22 16:14:40 +08:00
|
|
|
|
## 🤝 商务合作
|
|
|
|
|
|
|
|
|
|
|
|
- [预约咨询](https://aao615odquw.feishu.cn/share/base/form/shrcnjw7QleretCLqh1nuPo1xxh)
|
|
|
|
|
|
|
2024-04-01 13:51:41 +08:00
|
|
|
|
## 👥 加入社区
|
|
|
|
|
|
|
2024-12-04 10:11:20 +08:00
|
|
|
|
扫二维码添加 RAGFlow 小助手,进 RAGFlow 交流群。
|
2024-04-01 13:51:41 +08:00
|
|
|
|
|
|
|
|
|
|
<p align="center">
|
2024-12-04 10:11:20 +08:00
|
|
|
|
<img src="https://github.com/infiniflow/ragflow/assets/7248/bccf284f-46f2-4445-9809-8f1030fb7585" width=50% height=50%>
|
2024-04-01 13:51:41 +08:00
|
|
|
|
</p>
|