From 9b80903e56e823e5c83df4f45b7a412b6c28ea3d Mon Sep 17 00:00:00 2001 From: wood chen <95951386+woodchen-ink@users.noreply.github.com> Date: Sun, 28 Jan 2024 00:07:33 +0800 Subject: [PATCH] =?UTF-8?q?=E5=B0=9D=E8=AF=95=E4=BF=AE=E5=A4=8D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- code/config.yaml | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 code/config.yaml diff --git a/code/config.yaml b/code/config.yaml new file mode 100644 index 0000000..8df530b --- /dev/null +++ b/code/config.yaml @@ -0,0 +1,38 @@ +# 是否启用日志。 +ENABLE_LOG: true +# 飞书 +APP_ID: cli_axxx +APP_SECRET: xxx +APP_ENCRYPT_KEY: xxx +APP_VERIFICATION_TOKEN: xxx +# 请确保和飞书应用管理平台中的设置一致。这里建议直接用 Feishu-OpenAI-Stream-Chatbot 作为机器人名称,这样的话,如果你有多个bot就好区分 +BOT_NAME: xxx +# openAI key 支持负载均衡 可以填写多个key 用逗号分隔 +OPENAI_KEY: sk-xxx,sk-xxx,sk-xxx +# 服务器配置 +HTTP_PORT: 9000 +HTTPS_PORT: 9001 +USE_HTTPS: false +CERT_FILE: cert.pem +KEY_FILE: key.pem +# openai 地址, 一般不需要修改, 除非你有自己的反向代理 +API_URL: https://oapi.czl.net +# 代理设置, 例如 "http://127.0.0.1:7890", ""代表不使用代理 +HTTP_PROXY: "" +# 访问OpenAi的 普通 Http请求的超时时间,单位秒,不配置的话默认为 550 秒 +OPENAI_HTTP_CLIENT_TIMEOUT: +# openai 指定模型, 更多见 https://platform.openai.com/docs/models/model-endpoint-compatibility 中 /v1/chat/completions +OPENAI_MODEL: gpt-3.5-turbo + +# AZURE OPENAI +AZURE_ON: false # set to true to use Azure rather than OpenAI +AZURE_API_VERSION: 2023-03-15-preview # 2023-03-15-preview or 2022-12-01 refer https://learn.microsoft.com/en-us/azure/cognitive-services/openai/reference#completions +AZURE_RESOURCE_NAME: xxxx # you can find in endpoint url. Usually looks like https://{RESOURCE_NAME}.openai.azure.com +AZURE_DEPLOYMENT_NAME: xxxx # usually looks like ...openai.azure.com/openai/deployments/{DEPLOYMENT_NAME}/chat/completions. +AZURE_OPENAI_TOKEN: xxxx # Authentication key. We can use Azure Active Directory Authentication(TBD). + +## 访问控制 +# 是否启用访问控制。默认不启用。 +ACCESS_CONTROL_ENABLE: false +# 每个用户每天最多问多少个问题。默认为不限制. 配置成为小于等于0表示不限制。 +ACCESS_CONTROL_MAX_COUNT_PER_USER_PER_DAY: 0