Repository navigation
refactor: migrate to New API with SQLite - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
变更
旧部署需要 Hub、CLIProxyAPI 和外部数据库,维护成本较高。现在改成固定版本的 New API 单容器,使用 SQLite 保存账号、渠道、令牌和消费记录,默认监听
127.0.0.1:23000。new-api-runtime,支持 Podman / Docker、私有本机状态、健康检查、在线 SQLite 一致备份及恢复到空目录。new-api-runtime/services.newApiRuntime;已有 dev-runtime 继续单独管理网关,不重复启用服务。deploy/节点部署和 SSH 工具;历史内容仍可通过 Git 恢复。Docker 首次选择的引擎和项目名保存到私有
.env;容器按宿主 UID/GID 写入 SQLite,避免备份受 root 文件所有权影响。文档补充本地 CPU 过载拒绝的关闭方法和 1 倍率额度记账。验证
nix flake check --no-update-lock-file:x86_64-linux 包和检查通过;aarch64-linux 未实际构建。迁移注意
这是不兼容接口迁移。旧服务、凭据和数据库不自动删除;按
docs/migration.md完成导出、验证和切换。OAuth 订阅凭据及旧 Hub 历史统计不直接导入,新部署也不捏造模型价格。仓库 URL 保持不变,旧 GHCR 镜像标签不会被替换为 New API。