Cherry Studio 客户端优化
All checks were successful
Build and Push OCI GenAI Gateway Docker Image / docker-build-push (push) Successful in 35s
All checks were successful
Build and Push OCI GenAI Gateway Docker Image / docker-build-push (push) Successful in 35s
This commit is contained in:
90
.env.example
90
.env.example
@@ -1,23 +1,37 @@
|
||||
# API Settings
|
||||
# ============================================
|
||||
# API 服务设置
|
||||
# ============================================
|
||||
# API 服务标题(显示在 OpenAPI 文档中)
|
||||
API_TITLE=OCI GenAI to OpenAI API Gateway
|
||||
# API 版本号
|
||||
API_VERSION=0.0.1
|
||||
# API 路由前缀(符合 OpenAI API 规范,不建议修改)
|
||||
API_PREFIX=/v1
|
||||
# 服务监听端口
|
||||
API_PORT=8000
|
||||
# 服务监听地址(0.0.0.0 表示监听所有网络接口)
|
||||
API_HOST=0.0.0.0
|
||||
# 调试模式(生产环境应设置为 false)
|
||||
DEBUG=false
|
||||
|
||||
# Authentication
|
||||
# Comma-separated list of API keys for authentication
|
||||
# These are the keys clients will use in Authorization: Bearer <key>
|
||||
# ============================================
|
||||
# 认证设置
|
||||
# ============================================
|
||||
# API 密钥列表(JSON 数组格式)
|
||||
# 客户端通过 Authorization: Bearer <key> 头进行认证
|
||||
# 支持配置多个密钥,用于不同的客户端或应用
|
||||
# 示例:
|
||||
# 单个密钥:API_KEYS=["sk-your-secret-key"]
|
||||
# 多个密钥:API_KEYS=["sk-admin-key","sk-user-key","sk-app-key"]
|
||||
API_KEYS=["sk-oci-genai-default-key"]
|
||||
|
||||
# ============================================
|
||||
# OCI Configuration
|
||||
# OCI 配置
|
||||
# ============================================
|
||||
# Path to OCI config file (usually ~/.oci/config)
|
||||
# OCI 配置文件路径(通常为 ~/.oci/config)
|
||||
OCI_CONFIG_FILE=~/.oci/config
|
||||
|
||||
# Profile names in the OCI config file
|
||||
# OCI 配置文件中的 profile 名称
|
||||
# 支持单个或多个 profile,多个 profile 用逗号分隔
|
||||
# 多个 profile 时会自动使用轮询(round-robin)负载均衡
|
||||
# 示例:
|
||||
@@ -26,51 +40,61 @@ OCI_CONFIG_FILE=~/.oci/config
|
||||
# 注意:每个 profile 在 ~/.oci/config 中必须包含 region 和 tenancy (作为 compartment_id)
|
||||
OCI_CONFIG_PROFILE=DEFAULT
|
||||
|
||||
# Authentication type: api_key or instance_principal
|
||||
# 认证类型:api_key 或 instance_principal
|
||||
OCI_AUTH_TYPE=api_key
|
||||
|
||||
# OCI Client Timeout Settings
|
||||
# Connect timeout: Maximum time (in seconds) to establish connection to OCI API
|
||||
# OCI 客户端超时设置
|
||||
# 连接超时:与 OCI API 建立连接的最大时间(秒)
|
||||
OCI_CONNECT_TIMEOUT=10
|
||||
# Read timeout: Maximum time (in seconds) to wait for OCI API response
|
||||
# Increase this value for long-running requests (e.g., complex conversations)
|
||||
# 读取超时:等待 OCI API 响应的最大时间(秒)
|
||||
# 处理长时间运行的请求时(例如复杂对话)可增加此值
|
||||
OCI_READ_TIMEOUT=360
|
||||
|
||||
# Optional: Direct endpoint for dedicated models
|
||||
# 可选:专用模型的直接端点
|
||||
# GENAI_ENDPOINT=https://your-dedicated-endpoint
|
||||
|
||||
# Model Settings
|
||||
# Note: Available models are dynamically loaded from OCI at startup
|
||||
# Use GET /v1/models to see all available models
|
||||
MAX_TOKENS=4096
|
||||
# ============================================
|
||||
# 模型设置
|
||||
# ============================================
|
||||
# 注意:可用模型在启动时从 OCI 动态加载
|
||||
# 使用 GET /v1/models 查看所有可用模型
|
||||
MAX_TOKENS=8192
|
||||
TEMPERATURE=0.7
|
||||
|
||||
# Embedding Settings
|
||||
# Truncate strategy for embeddings: END or START
|
||||
# ============================================
|
||||
# 嵌入向量设置
|
||||
# ============================================
|
||||
# 嵌入向量的截断策略:END(保留开头,截断末尾)或 START(保留末尾,截断开头)
|
||||
EMBED_TRUNCATE=END
|
||||
|
||||
# Streaming Settings
|
||||
# Global streaming on/off switch
|
||||
# Set to false to disable streaming for all requests (overrides client stream=true)
|
||||
# ============================================
|
||||
# 流式响应设置
|
||||
# ============================================
|
||||
# 全局流式响应开关
|
||||
# 设置为 false 将禁用所有流式请求(覆盖客户端的 stream=true 设置)
|
||||
ENABLE_STREAMING=true
|
||||
# Chunk size for simulated streaming (fallback mode only)
|
||||
# Only used when OCI returns non-streaming response
|
||||
# 模拟流式传输的分块大小(仅在回退模式下使用)
|
||||
# 仅当 OCI 返回非流式响应时使用
|
||||
STREAM_CHUNK_SIZE=1024
|
||||
|
||||
# Logging
|
||||
# Log level: DEBUG, INFO, WARNING, ERROR, CRITICAL
|
||||
# ============================================
|
||||
# 日志设置
|
||||
# ============================================
|
||||
# 日志级别:DEBUG, INFO, WARNING, ERROR, CRITICAL
|
||||
LOG_LEVEL=INFO
|
||||
|
||||
# Enable detailed request/response logging for debugging
|
||||
# LOG_REQUESTS: Print incoming request details (method, URL, headers, body)
|
||||
# LOG_RESPONSES: Print outgoing response details (status, headers, body)
|
||||
# Note: Sensitive data (like API keys) are automatically filtered from logs
|
||||
# 启用详细的请求/响应日志记录以进行调试
|
||||
# LOG_REQUESTS:打印传入请求的详细信息(方法、URL、请求头、请求体)
|
||||
# LOG_RESPONSES:打印发出响应的详细信息(状态码、响应头、响应体)
|
||||
# LOG_STREAMING:打印流式响应内容(⚠️ 增加内存使用和日志大小)
|
||||
# 注意:敏感数据(如 API 密钥)会自动从日志中过滤
|
||||
LOG_REQUESTS=false
|
||||
LOG_RESPONSES=false
|
||||
LOG_STREAMING=true
|
||||
|
||||
# Log file path (optional, if not set logs only to console)
|
||||
# 日志文件路径(可选,如果未设置则仅输出到控制台)
|
||||
LOG_FILE=./logs/app.log
|
||||
# Max log file size in MB (default: 10)
|
||||
# 日志文件最大大小(MB,默认:10)
|
||||
LOG_FILE_MAX_SIZE=10
|
||||
# Number of backup log files to keep (default: 5)
|
||||
# 保留的备份日志文件数量(默认:5)
|
||||
LOG_FILE_BACKUP_COUNT=5
|
||||
|
||||
Reference in New Issue
Block a user