Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: 新增黑名单用户及VIP用户处理逻辑，同时修改ALLOW_USERS的校验为userid（SenderStaffId），将用户相关校验统一为userid #190

Merged
merged 20 commits into from
Apr 9, 2023
Merged

feat: 新增黑名单用户及VIP用户处理逻辑，同时修改ALLOW_USERS的校验为userid（SenderStaffId），将用户相关校验统一为userid #190

Changes from 1 commit
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
170b036
perf: 新增VIP用户处理逻辑（管理员和VIP用户不受请求次数限制），同时修改ALLOW_USERS的校验为userid（Sender…
ffinly Apr 9, 2023
cc7bbd1
Update process_request.go
ffinly Apr 9, 2023
ad10e3a
Update README.md
ffinly Apr 9, 2023
37c94a9
Update config.example.yml
ffinly Apr 9, 2023
f3e8b74
Update docker-compose.yml
ffinly Apr 9, 2023
b6fa52d
Update tools.go
ffinly Apr 9, 2023
69e01ed
Update main.go
ffinly Apr 9, 2023
485b84a
Update README.md
ffinly Apr 9, 2023
ef67c52
Update config.example.yml
ffinly Apr 9, 2023
05de949
Update config.go
ffinly Apr 9, 2023
06098f8
Update docker-compose.yml
ffinly Apr 9, 2023
687a762
Update main.go
ffinly Apr 9, 2023
0303a4a
Update main.go
ffinly Apr 9, 2023
c79fb61
Update main.go
ffinly Apr 9, 2023
0fd72cc
Update main.go
ffinly Apr 9, 2023
e85d421
Update config.example.yml
ffinly Apr 9, 2023
664e19b
Update README.md
ffinly Apr 9, 2023
51d9595
Update main.go
ffinly Apr 9, 2023
bfad3ff
Update main.go
ffinly Apr 9, 2023
b80658e
Update main.go
ffinly Apr 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update README.md
  • Loading branch information
@ffinly
ffinly committed Apr 9, 2023
commit 664e19b4ed43f537dd87e9ef25f79b41c314e75d
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -184,7 +184,7 @@ $ docker run -itd --name chatgpt -p 8090:8090 \
> 运行命令中映射的配置文件参考下边的[配置文件说明](#%E9%85%8D%E7%BD%AE%E6%96%87%E4%BB%B6%E8%AF%B4%E6%98%8E)。

- `📢 注意：`如果使用docker部署，那么PORT参数不需要进行任何调整。
- `📢 注意：`ALLOW_GROUPS,ALLOW_USERS,DENY_USERS,VIP_USERS,ADMIN_USERS 参数为数组，如果需要指定多个，可用英文逗号分割。
- `📢 注意：`ALLOW_GROUPS,ALLOW_USERS,DENY_USERS,VIP_USERS,ADMIN_USERS 参数为数组，如果需要指定多个，可用英文逗号分割。outgoing机器人模式下这些参数无效。
- `📢 注意：`如果服务器节点本身就在国外或者自定义了`BASE_URL`，那么就把`HTTP_PROXY`参数留空即可。
- `📢 注意：`如果使用docker部署，那么proxy地址可以直接使用如上方式部署，`host.docker.internal`会指向容器所在宿主机的IP，只需要更改端口为你的代理端口即可。参见：[Docker容器如何优雅地访问宿主机网络](https://wiki.eryajf.net/pages/674f53/)

Expand Down Expand Up @@ -420,7 +420,7 @@ chat_type: "0"
# 对话聊天时，如下三个满足其一即可通过校验
allow_groups:
- "学无止境"
# 以下 allow_users、deny_users、vip_users、admin_users 配置中填写的是用户的userid
# 以下 allow_users、deny_users、vip_users、admin_users 配置中填写的是用户的userid，outgoing机器人模式下不适用这些配置
# 比如 ["1301691029702722","1301691029702733"]，这个信息需要在钉钉管理后台的通讯录当中获取：https://oa.dingtalk.com/contacts.htm#/contacts
# 哪些用户可以进行对话，如果留空，则表示允许所有用户，如果要限制，则列表中写用户的userid
allow_users: []
Expand Down