win10环境下dify本地化部署及使用时可能修改的配置
首先打开dify所在目录,进入到docker文件夹下,如没有.env文件,请将.env.example文件复制并改名为.env。设置WORKER_TIMEOUT(我这里简单粗暴的+15,操作有待商榷)(这里我的路径是:D:\dify-0.15.3\docker)同时,还需要修改docker-compose.yaml文件。将internal: true注释掉。
·
首先打开dify所在目录,进入到docker文件夹下,如没有.env文件,请将.env.example文件复制并改名为.env
(这里我的路径是:D:\dify-0.15.3\docker)
知识库上传文件大小及数量限制
# ------------------------------
# Knowledge Configuration
# ------------------------------
# Upload file size limit, default 15M.
UPLOAD_FILE_SIZE_LIMIT=15
# The maximum number of files that can be uploaded at a time, default 5.
UPLOAD_FILE_BATCH_LIMIT=5
大模型生成结果最大token限制
# ------------------------------
# Model Configuration
# ------------------------------
# The maximum number of tokens allowed for prompt generation.
# This setting controls the upper limit of tokens that can be used by the LLM
# when generating a prompt in the prompt generation tool.
# Default: 512 tokens.
PROMPT_GENERATION_MAX_TOKENS=512
# The maximum number of tokens allowed for code generation.
# This setting controls the upper limit of tokens that can be used by the LLM
# when generating code in the code generation tool.
# Default: 1024 tokens.
CODE_GENERATION_MAX_TOKENS=1024
工作流http请求节点响应大小限制
# HTTP request node in workflow configuration
HTTP_REQUEST_NODE_MAX_BINARY_SIZE=4194304
HTTP_REQUEST_NODE_MAX_TEXT_SIZE=1048576
工作流http请求节点访问其他主机上的服务
# Environment Variables for sandbox Service
# The API key for the sandbox service
SANDBOX_API_KEY=dify-sandbox
# The mode in which the Gin framework runs
SANDBOX_GIN_MODE=release
# The timeout for the worker in seconds
SANDBOX_WORKER_TIMEOUT=15
# Enable network for the sandbox service
SANDBOX_ENABLE_NETWORK=true
# HTTP proxy URL for SSRF protection
SANDBOX_HTTP_PROXY=http://ssrf_proxy:3128
# HTTPS proxy URL for SSRF protection
SANDBOX_HTTPS_PROXY=http://ssrf_proxy:3128
# The port on which the sandbox service runs
SANDBOX_PORT=8194
同时,还需要修改docker-compose.yaml文件
networks:
# create a network between sandbox, api and ssrf_proxy, and can not access outside.
ssrf_proxy_network:
driver: bridge
internal: true
milvus:
driver: bridge
opensearch-net:
driver: bridge
# internal: true
将internal: true注释掉
工作流http请求节点请求超时限制
sandbox:
image: langgenius/dify-sandbox:0.2.10
restart: always
environment:
# The DifySandbox configurations
# Make sure you are changing this key for your deployment with a strong key.
# You can generate a strong key using `openssl rand -base64 42`.
API_KEY: ${SANDBOX_API_KEY:-dify-sandbox}
GIN_MODE: ${SANDBOX_GIN_MODE:-release}
WORKER_TIMEOUT: ${SANDBOX_WORKER_TIMEOUT:+15}
ENABLE_NETWORK: ${SANDBOX_ENABLE_NETWORK:-true}
HTTP_PROXY: ${SANDBOX_HTTP_PROXY:-http://ssrf_proxy:3128}
HTTPS_PROXY: ${SANDBOX_HTTPS_PROXY:-http://ssrf_proxy:3128}
SANDBOX_PORT: ${SANDBOX_PORT:-8194}
volumes:
- ./volumes/sandbox/dependencies:/dependencies
healthcheck:
test: [ 'CMD', 'curl', '-f', 'http://localhost:8194/health' ]
networks:
- ssrf_proxy_network
设置WORKER_TIMEOUT(我这里简单粗暴的+15,操作有待商榷)
通过.env,docker-compose.yaml,docker-compose.middleware.yaml这三个配置文件,可以解决绝大多数因为配置问题而导致的工作节点报错情况,文件当中还有其他很多配置参数,目前只总结了自己所遇到的一些情况,方便下次回顾
更多推荐
所有评论(0)