chore(release): 生产 seed 与 compose 漂移闭环、回滚重建容器、PR #29 与发布证据入库
- AUTH-D2 生产 db:seed 已执行:esbuild 打包真 seed → 生产库副本演练 → 逐表差异 (Permission +63/−0、ContentItem 37→38、24 条随 seed 源更新、User 口令逐字节未变) → 停容器窗口内用生产镜像跑 → 事后取回比对。快照 prod.db.bak.20261008_174734-preseed - H compose 漂移已消除:先 diff 证明只差挂载一行,备份后同步并重建, docker inspect 现取 ./uploads -> /app/public/uploads - I cmd_rollback 追加 docker-compose build && up -d 与就绪轮询,并复用资源级 verify - J PR #29 建成(qa/seal-2026-09-28 → dev,mergeable true);同时作废「本环境无 Gitea token」这条由 `2>/dev/null` 吞掉报错造成的假事实,教训入 lessons §5.35 - 新登记 K:navigation 与 site-config 在 seed 的 permissionMatrix 里无授予项 - 证据:docs/acceptance/2026-10-08-release/(build/deploy/type-check/lint 日志、 seed 演练与逐表差异脚本及输出)
This commit is contained in:
1 parent
81bdeebc64
commit
c0c41eb528
10 files changed
+5805
-6
No files matched your search
@@ -420,6 +420,36 @@ cmd_rollback() {
|
||||
fi
|
||||
"
|
||||
|
||||
# 回滚必须连 Next.js 容器一起回:Dockerfile.prod 是把 dist/standalone + dist/static + public
|
||||
# 拷进镜像的,只恢复宿主 dist/ 而让容器继续跑新代码,会得到「旧静态资源 + 新服务端」的
|
||||
# Server Reference ID 不匹配(页面 200 但 hydration/资源引用错乱)。2026-10-08 复盘补上。
|
||||
log "📋 用回滚后的产物重建 Next.js 容器 ($NEXTJS_CONTAINER)"
|
||||
run_remote "
|
||||
set -e
|
||||
cd '$REMOTE_PROJECT_DIR'
|
||||
if [ -f '$COMPOSE_FILE' ]; then
|
||||
$COMPOSE_CMD -f '$COMPOSE_FILE' build
|
||||
$COMPOSE_CMD -f '$COMPOSE_FILE' up -d
|
||||
READY=0
|
||||
for i in \$(seq 1 30); do
|
||||
if curl -fsS -o /dev/null --max-time 3 http://127.0.0.1:3000/ 2>/dev/null; then
|
||||
READY=1
|
||||
break
|
||||
fi
|
||||
sleep 2
|
||||
done
|
||||
if [ \"\$READY\" = \"1\" ]; then
|
||||
echo \"✅ $NEXTJS_CONTAINER 已按回滚产物重建并就绪\"
|
||||
else
|
||||
echo \"❌ $NEXTJS_CONTAINER 重建后未就绪,请检查容器日志\"
|
||||
exit 1
|
||||
fi
|
||||
else
|
||||
echo \"⚠️ 未找到 $COMPOSE_FILE,跳过容器重建(此时回滚仅覆盖 nginx 侧静态资源)\"
|
||||
fi
|
||||
"
|
||||
|
||||
# 回滚同样要满足资源级断言:只查 HTML 页会把破站判成回滚成功
|
||||
if verify_remote; then
|
||||
log ""
|
||||
log "🎉 回滚成功!"
|
||||
|
||||
Reference in new issue
Block a user