We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
青龙很多报错,基本鉴于拉库不完整,超时等,我推荐在青龙版本中植入getIP库,对面板客户端IP进行监控,如果是墙内IP就自动拉墙内的库,墙外就拉墙外的库,两个库之间互为镜像,也可以通过全局变量指定拉取的库的位置
这样对兼容性的修复比较好,可以省去很多因为拉库不完整带来的bug修复量,专注于脚本bug修复即可,你要觉得这个方案可行,可以用比如gitee gitcode 或者自行部署的加速节点,这种节点我有很多
The text was updated successfully, but these errors were encountered:
虽然,但是...... 这不是使用者自己要解决的问题吗
Sorry, something went wrong.
话是这样没错 但是 我看用户群了 一大半使用者,挂梯子都整不明白,所以是不是参考青龙面板原作者的做法在国内设置一个备用节点,来解决莫名其妙的报错,不然用户群里一堆的报错问题,都是拉库不全造成的
No branches or pull requests
确认
建议内容
青龙很多报错,基本鉴于拉库不完整,超时等,我推荐在青龙版本中植入getIP库,对面板客户端IP进行监控,如果是墙内IP就自动拉墙内的库,墙外就拉墙外的库,两个库之间互为镜像,也可以通过全局变量指定拉取的库的位置
这样对兼容性的修复比较好,可以省去很多因为拉库不完整带来的bug修复量,专注于脚本bug修复即可,你要觉得这个方案可行,可以用比如gitee gitcode 或者自行部署的加速节点,这种节点我有很多
The text was updated successfully, but these errors were encountered: