一、導讀
環境：Ubuntu 24.04、open Euler 23.03、Windows 11、WSL 2、Python 3.10 、bisheng 1.2.0
背景：需要bisheng二開商用，故而此處進行本地部署，便于后期調試開發
時間：20250612
說明：bisheng的1.2版本部署與1.1.1有些許不同，故另開一章
注意：本節基于下面章節的內容，如有疑問，請閱讀：
bisheng系列（一）- 本地部署（Docker）
bisheng系列（二）- 本地部署（前后端）
?
二、停止前后端的docker
bisheng共計9個容器，需要獨立代碼啟動前后端，則需要將前后端的容器停止
1、停止并刪除所有容器
命令：
docker-compose down效果?
jack@Laptop-L14-gen4:~/bisheng-blog/bisheng/docker/bisheng-main/docker$ docker-compose down
Stopping bisheng-frontend ... done
Stopping bisheng-backend ... done
Stopping milvus-standalone ... done
Stopping bisheng-es ... done
Stopping bisheng-office ... done
Stopping milvus-etcd ... done
Stopping bisheng-mysql ... done
Stopping bisheng-redis ... done
Stopping milvus-minio ... done
Removing bisheng-frontend ... done
Removing bisheng-backend ... done
Removing milvus-standalone ... done
Removing bisheng-es ... done
Removing bisheng-office ... done
Removing milvus-etcd ... done
Removing bisheng-mysql ... done
Removing bisheng-redis ... done
Removing milvus-minio ... done
Removing network docker_default
jack@Laptop-L14-gen4:~/bisheng-blog/bisheng/docker/bisheng-main/docker$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5257cf9b2426 qdrant/qdrant "./entrypoint.sh" 3 weeks ago Exited (255) 2 weeks ago 0.0.0.0:6333-6334->6333-6334/tcp, :::6333-6334->6333-6334/tcp distracted_lamport
b28179c3b79b qdrant/qdrant "./entrypoint.sh" 3 weeks ago Exited (255) 3 weeks ago 0.0.0.0:6333-6334->6333-6334/tcp, :::6333-6334->6333-6334/tcp bold_beaver
b00d21f614f7 hello-world "/hello" 3 weeks ago Exited (0) 3 weeks ago objective_khayyam
114b2a816fae ubuntu1:8080 "/bin/sh -c 'npm i &…" 7 weeks ago Exited (255) 7 weeks ago 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp light_house通過上述命令說明，bisheng的9個容器停止并刪除成功
2、配置docker-compse
通過編輯docker-compose.yml文件，刪除前后端的啟動項，修改后內容如下：
services:mysql:container_name: bisheng-mysqlimage: mysql:8.0ports:- "3306:3306"environment:MYSQL_ROOT_PASSWORD: "1234" # 數據庫密碼，如果修改需要同步修改bisheng/congfig/config.yaml配置database_url的mysql連接密碼MYSQL_DATABASE: bishengTZ: Asia/Shanghaivolumes:- ${DOCKER_VOLUME_DIRECTORY:-.}/mysql/conf/my.cnf:/etc/mysql/my.cnf- ${DOCKER_VOLUME_DIRECTORY:-.}/mysql/data:/var/lib/mysqlhealthcheck:test: ["CMD-SHELL", "exit | mysql -u root -p$$MYSQL_ROOT_PASSWORD"]start_period: 30sinterval: 20stimeout: 10sretries: 4restart: on-failureredis:container_name: bisheng-redisimage: redis:7.0.4ports:- "6379:6379"environment:TZ: Asia/Shanghaivolumes:- ${DOCKER_VOLUME_DIRECTORY:-.}/data/redis:/data- ${DOCKER_VOLUME_DIRECTORY:-.}/redis/redis.conf:/etc/redis.confcommand: redis-server /etc/redis.confhealthcheck:test: ["CMD-SHELL", 'redis-cli ping|grep -e "PONG\|NOAUTH"']interval: 10stimeout: 5sretries: 3restart: on-failureoffice:container_name: bisheng-officeimage: onlyoffice/documentserver:7.1.1ports:- "8701:80"environment:TZ: Asia/ShanghaiJWT_ENABLED: "false"volumes:- ${DOCKER_VOLUME_DIRECTORY:-.}/office/bisheng:/var/www/onlyoffice/documentserver/sdkjs-plugins/bishengcommand: bash -c "supervisorctl restart all"restart: on-failureelasticsearch:container_name: bisheng-esimage: docker.io/bitnami/elasticsearch:8.12.0user: rootports:- "9200:9200"- "9300:9300"environment:TZ: Asia/Shanghaivolumes:- ${DOCKER_VOLUME_DIRECTORY:-.}/data/es:/bitnami/elasticsearch/datarestart: on-failureetcd:container_name: milvus-etcdimage: quay.io/coreos/etcd:v3.5.5environment:ETCD_AUTO_COMPACTION_MODE: revisionETCD_AUTO_COMPACTION_RETENTION: "1000"ETCD_QUOTA_BACKEND_BYTES: "4294967296"ETCD_SNAPSHOT_COUNT: "50000"TZ: Asia/Shanghaivolumes:- ${DOCKER_VOLUME_DIRECTORY:-.}/data/milvus-etcd:/etcdcommand: etcd -advertise-client-urls=http://127.0.0.1:2379 -listen-client-urls http://0.0.0.0:2379 --data-dir /etcdrestart: on-failurehealthcheck:test: ["CMD", "etcdctl", "endpoint", "health"]interval: 30stimeout: 20sretries: 3minio:container_name: milvus-minioimage: minio/minio:RELEASE.2023-03-20T20-16-18Zenvironment:MINIO_ACCESS_KEY: minioadminMINIO_SECRET_KEY: minioadminports:- "9100:9000"- "9101:9001"volumes:- /etc/localtime:/etc/localtime:ro- ${DOCKER_VOLUME_DIRECTORY:-.}/data/milvus-minio:/minio_datacommand: minio server /minio_data --console-address ":9001"restart: on-failurehealthcheck:test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]interval: 30stimeout: 20sretries: 3milvus:container_name: milvus-standaloneimage: milvusdb/milvus:v2.3.3command: ["milvus", "run", "standalone"]security_opt:- seccomp:unconfinedenvironment:ETCD_ENDPOINTS: etcd:2379MINIO_ADDRESS: minio:9000volumes:- /etc/localtime:/etc/localtime:ro- ${DOCKER_VOLUME_DIRECTORY:-.}/data/milvus:/var/lib/milvusrestart: on-failurehealthcheck:test: ["CMD", "curl", "-f", "http://localhost:9091/healthz"]start_period: 90sinterval: 30stimeout: 20sretries: 3ports:- "19530:19530"- "9091:9091"depends_on:- etcd- minio3、啟動其余容器
jack@Laptop-L14-gen4:~/bisheng-blog/bisheng/docker/bisheng-main/docker$ docker-compose up -d
Creating network "docker_default" with the default driver
Creating milvus-etcd ... done
Creating bisheng-redis ... done
Creating bisheng-mysql ... done
Creating bisheng-office ... done
Creating milvus-minio ... done
Creating bisheng-es ... done
Creating milvus-standalone ... done4、前后端代碼
前后端的代碼分別時：
后端：bisheng/src/backend
前端：bisheng/src/frontend
三、后端啟動
通過修改部分文件，使后端可以連接到相關的容器服務
后端在open Euler 23.03啟動，我使用vscode來修改相關文件
1、克隆源碼
git clone https://github.com/dataelement/bisheng.git2、安裝相關環境
sudo yum -y install python3-pip python3-devel gcc g++ 3、安裝poetry
pip install poetry==1.8.24、項目環境
# 在當前項目根目錄下生成環境
poetry config virtualenvs.create true# 安裝環境所需的模塊
poetry install# 在openEuler環境需要該包
poetry add opencv-python-headless
?安裝后，看下安裝過程是否存在異常，如下為正常
...... - Installing types-pillow (9.5.0.6)- Installing types-pyyaml (6.0.12.20250516)- Installing types-requests (2.32.0.20250515)
......Writing lock fileInstalling the current project: bisheng (1.1.1)?
5、配置文件
此處配置文件特指其余七個容器的連接配置
將/bisheng/docker/bisheng/config/config.yaml?復制到指定目錄下，并修改如下：
# 修改后的文件內容，刪除了注釋的內容database_url:"mysql+pymysql://root:gAAAAABlp4b4c59FeVGF_OQRVf6NOUIGdxq8246EBD-b0hdK_jVKRs1x4PoAn0A6C5S6IiFKmWn0Nm5eBUWu-7jxcqw6TiVjQA==@0.0.0.0:3306/bisheng?charset=utf8mb4"# 緩存配置 redis://[[username]:[password]]@localhost:6379/0
# 普通模式:
redis_url: "redis://0.0.0.0:6379/1"# celery的broken地址
celery_redis_url: "redis://0.0.0.0:6379/2"# 知識庫的milvus和es配置 支持使用 !env ${PATH} 填寫環境變量的值, 若環境變量不存在則會報錯
vector_stores:milvus:connection_args: '{"host":"0.0.0.0","port":"9530","user":"","password":"","secure":false}'is_partition: truepartition_suffix: "1"elasticsearch:url: 'http://0.0.0.0:9200'ssl_verify: '{"basic_auth": ("elastic", "elastic")}'# 對象存儲， 目前只支持minio
object_storage:type: miniominio:schema: falsecert_check: falseendpoint: '0.0.0.0:9100'sharepoint: '0.0.0.0:9100'access_key: minioadminsecret_key: minioadminenvironment:env: devuns_support: ['png','jpg','jpeg','bmp','doc', 'docx', 'ppt', 'pptx', 'xls', 'xlsx', 'txt', 'md', 'html', 'pdf', 'csv', 'tiff']# 可根據loguru的文檔配置不同 handlers
logger_conf:# 默認輸出到sys.stdout的日志級別, 大于等于此級別都會輸出level: DEBUG# 默認輸出格式format: '<level>[{time:YYYY-MM-DD HH:mm:ss.SSSSSS}] [{level.name} process-{process.id}-{thread.id} {name}:{line}]</level> - <level>trace={extra[trace_id]} {message}</level>'# 參考loguru.add()中的參數可以配置多個handlerhandlers:# 文件路徑，支持插入一些系統環境變量，若環境變量不存在則置空。例如 HOSTNAME: 主機名。后端會處理環境變量的替換- sink: "/home/jack/bisheng_11/backend/data/bisheng.log"# 日志級別level: INFO# 日志格式化函數，extra內支持trace_idformat: '<level>[{time:YYYY-MM-DD HH:mm:ss.SSSSSS}] [{level.name} process-{process.id}-{thread.id} {name}:{line}]</level> - <level>trace={extra[trace_id]} {message}</level>'# 每天的幾點進行切割rotation: "00:00"retention: "3 Days"enqueue: ture- sink: "/home/jack/bisheng_11/backend/data/statistic.log"level: INFO# 和原生不一樣，后端會將配置使用eval()執行轉為函數用來過濾特定日志級別。推薦lambdafilter: "lambda record: record['level'].name == 'INFO' and record['message'].startswith('k=s')"format: "[{time:YYYY-MM-DD HH:mm:ss.SSSSSS}]|{level}|BISHENG|{extra[trace_id]}||{process.id}|{thread.id}|||#EX_ERR:POS={name},line {line},ERR=500,EMSG={message}"rotation: "00:00"retention: "3 Days"enqueue: ture修改目的是將鏈接修改為0.0.0.0:端口，由于之前使用docker配置可以連接，但是當前由于使用代碼直接啟動，無法識別http://mysql:3306這種鏈接，故而需要修改
日志路徑修改是為了保證權限的問題
編輯bisheng/src/backend/bisheng/api/services/assistant_agent.py，修改文件路徑
# 原內容async def record_chat_history(self, message: List[Any]):# 記錄助手的聊天歷史if not os.getenv('BISHENG_RECORD_HISTORY'):returntry:os.makedirs('/app/data/history', exist_ok=True)with open(f'/app/data/history/{self.assistant.id}_{time.time()}.json',# 修改后async def record_chat_history(self, message: List[Any]):# 記錄助手的聊天歷史if not os.getenv('BISHENG_RECORD_HISTORY'):returntry:os.makedirs('/home/jack/bisheng/src/backend/data/history', exist_ok=True)with open(f'/home/jack/bisheng/src/backend/data/history/{self.assistant.id}_{time.time()}.json',處理fastapi_jwt_auth、langchain_openai的兼容性
patch -p1 < ./bisheng/patches/fastapi_jwt_auth.patch ./.venv/lib/python3.10/site-packages/fastapi_jwt_auth/config.pypatch -p1 < ./bisheng/patches/langchain_openai.patch ./.venv/lib/python3.10/site-packages/langchain_openai/chat_models/base.py
6、啟動項目
uvicorn bisheng.main:app --host 0.0.0.0 --port 7860 成功如下：
.
.
.
INFO: Started server process [64315]
INFO: Waiting for application startup.
[2025-05-19 11:25:20.152105] [2025-05-19 11:25:20.151985] [DEBUG process-64315-139958058770496 bisheng.interface.utils:91] - trace=1 Setting up LLM caching with InMemoryCache
[2025-05-19 11:25:20.153851] [2025-05-19 11:25:20.153779] [INFO process-64315-139958058770496 bisheng.interface.utils:93] - trace=1 LLM caching setup with InMemoryCache
[2025-05-19 11:25:20.189322] [2025-05-19 11:25:20.189129] [DEBUG process-64315-139958058770496 bisheng.database.service:59] - trace=1 Creating database and tables
[2025-05-19 11:25:20.564080] [2025-05-19 11:25:20.563913] [DEBUG process-64315-139958058770496 bisheng.database.service:79] - trace=1 Database and tables created successfully
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7860 (Press CTRL+C to quit)四、前端啟動
略（參考上一節中的前端配置即可）
![[技術積累]成熟的前端和后端開發框架](http://pic.xiahunao.cn/[技術積累]成熟的前端和后端開發框架)
![[論文閱讀] 系統架構 | 零售 IT 中的微服務與實時處理：開源工具鏈與部署策略綜述](http://pic.xiahunao.cn/[論文閱讀] 系統架構 | 零售 IT 中的微服務與實時處理：開源工具鏈與部署策略綜述)
