2025-10-09 14:43:27 +08:00
|
|
|
|
# 快速开始指南
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-14 16:37:25 +08:00
|
|
|
|
::: tip 提示
|
2025-12-26 18:47:06 +08:00
|
|
|
|
除了此文档网站外,用户还可以在 [Zread](https://zread.ai/xerrors/Yuxi-Know) 或 [DeepWiki](https://deepwiki.com/xerrors/Yuxi-Know) 平台查看自动生成的详细项目文档。
|
2025-10-14 16:37:25 +08:00
|
|
|
|
:::
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
|
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
## 快速开始
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
|
|
|
|
|
|
### 安装步骤
|
|
|
|
|
|
|
2026-01-25 23:03:50 +08:00
|
|
|
|
项目采用微服务架构,默认服务无需 GPU 支持。GPU 仅用于可选的 OCR 服务,可通过环境变量配置外部服务。
|
2025-10-14 16:37:25 +08:00
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
#### 1. 获取项目代码
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
# 克隆稳定版本
|
2026-01-24 12:36:24 +08:00
|
|
|
|
git clone --branch v0.5.0-beta2 --depth 1 https://github.com/xerrors/Yuxi-Know.git
|
2025-10-09 14:43:27 +08:00
|
|
|
|
cd Yuxi-Know
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
::: warning 版本说明
|
2026-01-23 23:19:39 +08:00
|
|
|
|
- `v0.4.4`: 稳定版本
|
2026-01-25 23:03:50 +08:00
|
|
|
|
- `v0.5.0-beta2`: 由于数据库重构使用 postgres,可能会存在数据库迁移问题,建议新用户使用,迁移指南详见 [迁移指南](https://xerrors.github.io/Yuxi-Know/latest/changelog/migrate_to_v0-5)。
|
2025-10-12 13:09:29 +08:00
|
|
|
|
- `main`: 最新开发版本(不稳定,新特性可能会导致新 bug)
|
2025-10-09 14:43:27 +08:00
|
|
|
|
:::
|
|
|
|
|
|
|
2025-12-15 10:27:59 +08:00
|
|
|
|
#### 2. 项目启动
|
|
|
|
|
|
|
2025-12-23 12:12:34 +08:00
|
|
|
|
**方法 1**:使用 init 脚本(推荐)
|
2025-12-15 10:27:59 +08:00
|
|
|
|
|
|
|
|
|
|
我们提供了自动化的初始化脚本,可以帮您完成环境配置和 Docker 镜像拉取:
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
# Linux/macOS
|
|
|
|
|
|
./scripts/init.sh
|
|
|
|
|
|
|
|
|
|
|
|
# Windows PowerShell
|
|
|
|
|
|
.\scripts\init.ps1
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
脚本会:
|
|
|
|
|
|
- 检查并创建 `.env` 文件
|
|
|
|
|
|
- 提示您输入 `SILICONFLOW_API_KEY`(必需)
|
|
|
|
|
|
- 提示您输入 `TAVILY_API_KEY`(可选,用于搜索服务)
|
|
|
|
|
|
- 自动拉取所有必需的 Docker 镜像
|
|
|
|
|
|
|
|
|
|
|
|
::: tip API Key 获取
|
|
|
|
|
|
- [硅基流动](https://cloud.siliconflow.cn/i/Eo5yTHGJ) 注册即送 14 元额度
|
|
|
|
|
|
- [Tavily](https://app.tavily.com/) 获取搜索服务 API Key(可选)
|
|
|
|
|
|
:::
|
|
|
|
|
|
|
2025-12-23 12:12:34 +08:00
|
|
|
|
**方法 2**:手动配置环境变量
|
2025-10-09 14:43:27 +08:00
|
|
|
|
|
|
|
|
|
|
复制环境变量模板并编辑:
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
2025-10-10 18:07:06 +08:00
|
|
|
|
cp .env.template .env
|
2025-10-09 14:43:27 +08:00
|
|
|
|
```
|
|
|
|
|
|
|
2025-12-03 12:59:43 +08:00
|
|
|
|
编辑 `.env` 文件,配置必需的 API 密钥,这里强烈建议先使用硅基流动的 API 和模型(DeepSeek)验证平台的功能无误后,再尝试切换到自己的模型:
|
2025-10-10 18:07:06 +08:00
|
|
|
|
|
|
|
|
|
|
|
2025-11-15 22:33:22 +08:00
|
|
|
|
<<< @/../.env.template#model_provider{bash 5}
|
2025-10-09 14:43:27 +08:00
|
|
|
|
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
::: tip 免费获取 API Key
|
|
|
|
|
|
[硅基流动](https://cloud.siliconflow.cn/i/Eo5yTHGJ) 注册即送 14 元额度,支持多种开源模型。
|
|
|
|
|
|
:::
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
#### 3. 启动服务
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
# 构建并启动所有服务
|
|
|
|
|
|
docker compose up --build
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
# 后台运行(推荐)
|
|
|
|
|
|
docker compose up --build -d
|
|
|
|
|
|
```
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2026-01-07 20:58:38 +08:00
|
|
|
|
**注意**:启动后,可能还需要一些时间,尤其是后端服务需要一段时间,请耐心等待 2-3 分钟。
|
|
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
#### 4. 访问系统
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
服务启动完成后,访问以下地址:
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-10 15:35:36 +08:00
|
|
|
|
- **Web 界面**: `http://localhost:5173`
|
|
|
|
|
|
- **API 文档**: `http://localhost:5050/docs`
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
#### 5. 停止服务
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
```bash
|
|
|
|
|
|
docker compose down
|
|
|
|
|
|
```
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-12-23 12:12:34 +08:00
|
|
|
|
## 对话
|
|
|
|
|
|
|
|
|
|
|
|
项目第一次启动后,会要求填写超级管理员账号和密码,请确保填写正确。
|
|
|
|
|
|
|
|
|
|
|
|
然后在智能体页面可以进行对话,在右侧可以配置提示词、模型、工具等参数。
|
|
|
|
|
|
|
|
|
|
|
|

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## 故障排除
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2026-01-07 20:58:38 +08:00
|
|
|
|
::: tip 调试面板
|
2026-01-25 23:03:50 +08:00
|
|
|
|
前端有个**调试面板**,在头像选项里,生产环境建议删除此特性。
|
2026-01-07 20:58:38 +08:00
|
|
|
|
:::
|
|
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
#### 查看服务状态
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
# 查看所有容器状态
|
|
|
|
|
|
docker ps
|
|
|
|
|
|
|
|
|
|
|
|
# 查看后端服务日志
|
|
|
|
|
|
docker logs api-dev -f
|
|
|
|
|
|
|
|
|
|
|
|
# 查看前端服务日志
|
|
|
|
|
|
docker logs web-dev -f
|
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
#### 常见问题
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
|
|
|
|
|
<details>
|
2025-10-09 14:43:27 +08:00
|
|
|
|
<summary><strong>Docker 镜像拉取失败</strong></summary>
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
|
|
|
|
|
如果拉取镜像失败,可以尝试手动拉取:
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
2025-11-15 20:55:04 +08:00
|
|
|
|
# Linux/macOS
|
2025-12-03 12:59:43 +08:00
|
|
|
|
bash docker/pull_image.sh python:3.12-slim
|
2025-11-15 20:55:04 +08:00
|
|
|
|
|
|
|
|
|
|
# Windows PowerShell
|
2025-12-03 12:59:43 +08:00
|
|
|
|
powershell -ExecutionPolicy Bypass -File docker/pull_image.ps1 python:3.12-slim
|
2025-10-08 22:58:30 +08:00
|
|
|
|
```
|
2025-10-09 14:43:27 +08:00
|
|
|
|
|
2025-12-15 09:00:26 +08:00
|
|
|
|
**离线镜像拉取方案**:
|
2025-10-09 14:43:27 +08:00
|
|
|
|
|
2025-10-08 22:58:30 +08:00
|
|
|
|
```bash
|
2026-01-25 23:03:50 +08:00
|
|
|
|
# 在有网络的环境保存镜像(镜像名称需要确认是否和实际一致,现有版本可能不是最新最全,需要检查)
|
2025-10-09 14:43:27 +08:00
|
|
|
|
bash docker/save_docker_images.sh # Linux/macOS
|
|
|
|
|
|
powershell -ExecutionPolicy Bypass -File docker/save_docker_images.ps1 # Windows
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
# 传输到目标设备
|
2025-10-08 22:58:30 +08:00
|
|
|
|
scp docker_images_xxx.tar <user>@<dev_host>:<path_to_save>
|
|
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
# 在目标设备加载镜像
|
2025-10-08 22:58:30 +08:00
|
|
|
|
docker load -i docker_images_xxx.tar
|
|
|
|
|
|
```
|
2025-10-09 14:43:27 +08:00
|
|
|
|
|
2025-10-08 22:58:30 +08:00
|
|
|
|
</details>
|
2025-10-09 14:43:27 +08:00
|
|
|
|
|
2025-10-08 22:58:30 +08:00
|
|
|
|
<details>
|
2025-10-09 14:43:27 +08:00
|
|
|
|
<summary><strong>构建失败</strong></summary>
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
2025-10-09 14:43:27 +08:00
|
|
|
|
如果构建失败,通常是网络问题,可以配置代理:
|
2025-10-08 22:58:30 +08:00
|
|
|
|
|
|
|
|
|
|
```bash
|
2025-12-15 09:00:26 +08:00
|
|
|
|
# Linux / macOS
|
2025-10-08 22:58:30 +08:00
|
|
|
|
export HTTP_PROXY=http://IP:PORT
|
|
|
|
|
|
export HTTPS_PROXY=http://IP:PORT
|
2025-12-15 09:00:26 +08:00
|
|
|
|
|
|
|
|
|
|
# Windows PowerShell
|
|
|
|
|
|
$env:HTTP_PROXY="http://IP:PORT"
|
|
|
|
|
|
$env:HTTPS_PROXY="http://IP:PORT"
|
2025-10-08 22:58:30 +08:00
|
|
|
|
```
|
2025-10-09 14:43:27 +08:00
|
|
|
|
|
|
|
|
|
|
如果已配置代理但构建失败,尝试移除代理后重试。
|
|
|
|
|
|
|
2026-01-14 17:32:19 +08:00
|
|
|
|
如果出现,FetchError: request to https://registry.npmjs.org/npm failed, reason: connect ECONNREFUSED 127.0.0.1:7890
|
|
|
|
|
|
|
|
|
|
|
|
新建一个终端重新执行,并确保没有代理干扰。
|
|
|
|
|
|
|
2025-10-08 22:58:30 +08:00
|
|
|
|
</details>
|
|
|
|
|
|
|
|
|
|
|
|
<details>
|
2025-10-09 14:43:27 +08:00
|
|
|
|
<summary><strong>Milvus 启动失败</strong></summary>
|
|
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
|
# 重启 Milvus 服务
|
|
|
|
|
|
docker compose up milvus -d
|
|
|
|
|
|
docker restart api-dev
|
|
|
|
|
|
```
|
|
|
|
|
|
|
2025-10-08 22:58:30 +08:00
|
|
|
|
</details>
|