Repository navigation
Conversation
- 清零 9 处过期口径(quick-start/docker/compose/.env.example/configuration/ production/troubleshooting/architecture/dev-setup),统一改为 「账号体系已具备;AUTH_ENFORCE=off(默认)时资源端点仍可匿名,对外暴露务必设 on」 - 新增 docs/getting-started/first-run.md(bootstrap 两条路径 / 加同事 / 忘记口令恢复通道 / 刷新掉登录口径);README 增「第一次启动会发生什么」 - configuration.md 补 7 个新变量条目 + 「鉴权开放口径」表(与 R-92 路由分类同源) - CHANGELOG 增未发布段:非破坏性默认值 + compose 只绑环回行为变更 + 迁移水位 - docs/AGENTS.md 索引补 first-run.md;全仓相对链接可达检查通过
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.
做了什么
对应 issue #228(R-103)。纯文档批次,零代码改动。
AUTH_ENFORCE=off(默认)时资源端点仍可匿名访问,对外暴露务必设on」并回链 first-run / 配置字典。验收命令grep -rnE "无登录、无鉴权|无登录态|待账号体系" docs/ README.md docker-compose.allinone.yml .env.example返回空(issue 里列的docs/pitfalls.md:76文件已不存在,实际为 9 处)。docs/getting-started/first-run.md(验收 3):首启向导、bootstrap 两条路径、加同事(/api/users管理员端点)、忘记口令 = 已知边界(ADMIN_RESET_TOKEN补设即开、单次有效、20200、单人部署处置)、「刷新是否掉登录」口径(token 只存内存,R-93/[P0] R-93 前端身份壳:登录页与路由守卫 / 刷新不掉登录 / 未认证与越权分档 #218 跟进)。AUTH_ENFORCE/AUTH_RATE_LIMIT_PER_MINUTE/ADMIN_USERNAME/ADMIN_PASSWORD/ADMIN_RESET_TOKEN/LOG_LEVEL/HEALTH_DETAIL七项逐条写默认值、留空语义、重启要求;CORS 行删掉「平台 API 无登录态」。HOST_BIND留给 219: compose 默认只绑环回 + HOST_BIND 显式放开 #239 自己的条目,避免重复。on态强制清单,与 R-92(issue [P0] R-92 资源端点强制鉴权渐进开关:AUTH_ENFORCE 三态(off/shadow/on)+ 路由分类守卫 #217)的路由分类规格同源;表内注明守卫测试语义。怎么做 / 事实来源
本批 env 分三类来源,PR 合入顺序须与实现同批(issue 原文要求):
ADMIN_*三件套、bootstrap token 语义、recover-admin 20200/api/users管理员端点(建号/重置/禁用)LOG_LEVEL、JSON 日志、stdoutHEALTH_DETAIL、/health/detail404 语义、/versionAUTH_ENFORCE三态 + 永久白名单清单AUTH_RATE_LIMIT_PER_MINUTE默认 10测试证据
docs/AGENTS.md文档清单无死链 ✅.md+.env.example注释 + compose 注释改动,不触任何运行时代码 —— 无后端/前端测试面,浏览器 E2E 不适用(无 UI 行为变化);冒烟形态由make serve现状保证。评审需留意
backend/migrations/00013_*.sql(版本号撞车):合入这批时需要重排其中一个,本 PR 的迁移水位措辞已写「以最终合入为准」。AUTH_ENFORCE/AUTH_RATE_LIMIT_PER_MINUTE两个条目按已批准的规格([P0] R-92 资源端点强制鉴权渐进开关:AUTH_ENFORCE 三态(off/shadow/on)+ 路由分类守卫 #217/[P0] R-87 认证端点限流与失败锁定(#75 的收窄切片) #203)先行成文,对应实现合入后若语义/默认值有出入,以实现为准改回本字典。docs/deployment/backup-restore.md的备份链接改成了文字提示(该文件在 227: R-102 备份 / 升级 / 回滚最小可用(backup-restore.md + backup.sh + upgrade.sh) #245 里,先行合入会成死链)。