Files
AIclinicalresearch/诊断问题.bat
AI Clinical Dev Team 9acbb0ae2b feat: complete Dify platform deployment (Day 18)
## Dify 閮ㄧ讲瀹屾垚 鉁?
### 瀹屾垚鐨勫伐浣?1. Docker 闀滃儚鍔犻€熷櫒閰嶇疆
   - 閰嶇疆 5 涓浗鍐呴暅鍍忔簮
   - 澶у箙鎻愬崌涓嬭浇閫熷害鍜屾垚鍔熺巼

2. Dify 闀滃儚鎷夊彇 (鍏?11 涓湇鍔?
   - langgenius/dify-api:1.9.1
   - langgenius/dify-web:1.9.1
   - postgres, redis, weaviate, nginx 绛?   - 鎬诲ぇ灏忕害 2GB锛岃€楁椂绾?15 鍒嗛挓

3. Dify 鏈嶅姟鍚姩
   - 鉁?nginx (80/443)
   - 鉁?api, worker, worker_beat
   - 鉁?web (3000)
   - 鉁?db (PostgreSQL), redis
   - 鉁?weaviate (鍚戦噺鏁版嵁搴?
   - 鉁?sandbox, plugin_daemon, ssrf_proxy

4. Dify 鍒濆鍖栭厤缃?   - 鍒涘缓绠$悊鍛樿处鍙?   - 鍒涘缓搴旂敤: AI Clinical Research
   - 鑾峰彇 API Key: app-VZRn0vMXdmltEJkvatHVGv5j

5. 鍚庣鐜閰嶇疆
   - DIFY_API_URL=http://localhost/v1
   - DIFY_API_KEY 宸查厤缃?
### 鏂囨。鏇存柊
- 鏂板: docs/05-姣忔棩杩涘害/Day18-Dify閮ㄧ讲瀹屾垚.md
- 鏇存柊: docs/04-寮€鍙戣鍒?寮€鍙戦噷绋嬬.md (Day 18 鏍囪涓哄畬鎴?

### 涓嬩竴姝?Day 19-24: 鐭ヨ瘑搴撶郴缁熷紑鍙?- Dify 瀹㈡埛绔皝瑁?- 鐭ヨ瘑搴撶鐞?CRUD
- 鏂囨。涓婁紶涓庡鐞?- @鐭ヨ瘑搴撻泦鎴?- RAG 闂瓟楠岃瘉

---
Progress: 閲岀▼纰?1 (MVP) 85% -> 鐭ヨ瘑搴撶郴缁熷紑鍙戜腑
2025-10-11 08:58:41 +08:00

118 lines
2.8 KiB
Batchfile
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
@echo off
chcp 65001 >nul
echo ========================================
echo 系统诊断工具
echo ========================================
echo.
echo [检查1] Docker运行状态...
docker ps >nul 2>&1
if errorlevel 1 (
echo ❌ Docker未运行
echo 解决方案: 启动Docker Desktop
) else (
echo ✅ Docker正在运行
echo.
echo 运行中的容器:
docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"
)
echo.
echo [检查2] PostgreSQL容器...
docker ps | findstr postgres >nul
if errorlevel 1 (
echo ❌ PostgreSQL容器未运行
echo 解决方案: docker-compose up -d
) else (
echo ✅ PostgreSQL容器正在运行
)
echo.
echo [检查3] Redis容器...
docker ps | findstr redis >nul
if errorlevel 1 (
echo ❌ Redis容器未运行
echo 解决方案: docker-compose up -d
) else (
echo ✅ Redis容器正在运行
)
echo.
echo [检查4] 后端服务...
curl -s http://localhost:3001/health >nul 2>&1
if errorlevel 1 (
echo ❌ 后端服务未响应
echo 解决方案:
echo 1. cd backend
echo 2. npm run dev
) else (
echo ✅ 后端服务正常
echo.
echo 健康检查响应:
curl -s http://localhost:3001/health
)
echo.
echo [检查5] 前端服务...
curl -s http://localhost:3000 >nul 2>&1
if errorlevel 1 (
echo ❌ 前端服务未响应
echo 解决方案:
echo 1. cd frontend
echo 2. npm run dev
) else (
echo ✅ 前端服务正常
)
echo.
echo [检查6] 后端环境配置...
if exist "backend\.env" (
echo ✅ backend\.env 文件存在
echo.
echo 检查API Keys配置:
findstr /C:"DEEPSEEK_API_KEY" backend\.env | findstr /V "your_" >nul
if errorlevel 1 (
echo ⚠️ DEEPSEEK_API_KEY 可能未配置
) else (
echo ✅ DEEPSEEK_API_KEY 已配置
)
findstr /C:"DASHSCOPE_API_KEY" backend\.env | findstr /V "your_" >nul
if errorlevel 1 (
echo ⚠️ DASHSCOPE_API_KEY 可能未配置
) else (
echo ✅ DASHSCOPE_API_KEY 已配置
)
) else (
echo ❌ backend\.env 文件不存在
echo 解决方案:
echo 1. cd backend
echo 2. copy .env.example .env
echo 3. 编辑 .env 文件填入API Keys
)
echo.
echo [检查7] 数据库迁移状态...
if exist "backend\prisma\migrations" (
echo ✅ 数据库迁移文件存在
) else (
echo ❌ 数据库迁移文件不存在
echo 解决方案:
echo 1. cd backend
echo 2. npx prisma migrate dev
)
echo.
echo ========================================
echo 诊断完成
echo ========================================
echo.
echo 如果所有检查都通过但仍有问题,请:
echo 1. 查看后端终端的完整日志
echo 2. 查看浏览器控制台的Network标签
echo 3. 运行: cd backend ^&^& npx prisma studio 检查数据库
echo.
pause