SHA256
按 deploy/ci-cd.md 方案把除推送触发之外的东西都准备好:
- customization/check.sh <base-url>: 把 preview.sh check 里的"定制生效"断言抽成
任意实例可跑的脚本(首页/页脚/meta/官网链接/登录页两张卡/无通行密钥方框/
无「工单」/无 example.com), 另加生产才有的 OIDC 入口 307 断言(404 = 认证源没注册上)。
实测对生产 17/17 通过。
- deploy/scripts/auto-deploy.sh: build.py -> compose up -d -> verify.sh + check.sh,
失败自动回滚到 deploy/.state/last-deployed; flock 串行; 结束时把 clone 所有权还给
ymy(job 容器里是 root); 内网验证强制不走代理。
- deploy/runner/{compose.yaml,config.yaml,.env.example}: act_runner v0.6.1 跑在容器里
(不需要 root), network: host + 同路径挂载部署克隆 + 宿主 docker CLI/compose 插件,
capacity 1 保证部署串行。
- .gitea/workflows/deploy.yml: push main + workflow_dispatch, [skip deploy] 跳过,
concurrency 串行, 只做"同步到 github.sha + 调 auto-deploy.sh"。
- .gitignore: deploy/.state/、deploy/runner/{.env,data/}。
依据见 deploy/ci-cd.md(含全部实测证据与待确认项)。
This commit is contained in:
Executable
+141
@@ -0,0 +1,141 @@
|
||||
#!/usr/bin/env bash
|
||||
# main 自动部署 —— 由 .gitea/workflows/deploy.yml 调用, 也可以手工执行。
|
||||
#
|
||||
# ./auto-deploy.sh # 部署当前 checkout
|
||||
# ./auto-deploy.sh <sha> # 部署指定提交
|
||||
#
|
||||
# 流程: build.py(生成+校验) → docker compose up -d → 验证(verify.sh + check.sh)
|
||||
# 任一步失败 → 回滚到 deploy/.state/last-deployed 记录的上一个成功提交。
|
||||
# 只动代码与挂载文件; 数据库/`.env`/备份目录全程不参与(见 deploy/ci-cd.md §6)。
|
||||
set -euo pipefail
|
||||
|
||||
REPO_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
|
||||
STATE_DIR="${REPO_DIR}/deploy/.state"
|
||||
STATE_FILE="${STATE_DIR}/last-deployed"
|
||||
PUBLIC_URL="${GITEA_PUBLIC_URL:-http://10.80.42.185/QA}"
|
||||
|
||||
# 本机/内网回环验证不能走代理, 否则会把 200 变成 502(见 deploy/README.md 陷阱 5)
|
||||
unset http_proxy https_proxy HTTP_PROXY HTTPS_PROXY
|
||||
export no_proxy='*' NO_PROXY='*'
|
||||
# 只补齐标准路径(append): 不要把 /usr/bin 提到最前面 —— 宿主上 /usr/bin/python3 是 3.6
|
||||
export PATH="${PATH}:/usr/local/bin:/usr/bin:/bin"
|
||||
|
||||
# build.py 用了 `from __future__ import annotations`, 需要 python3 >= 3.7。
|
||||
# 宿主: python3 在 ~/.local/bin(3.14), /usr/bin/python3 是 3.6(Rocky 8);
|
||||
# job 容器(Ubuntu 22.04): /usr/bin/python3 是 3.10。所以不能盲信 PATH 里的第一个。
|
||||
# (第一次实测就踩到: 把 /usr/bin 提前 → 用 3.6 跑 build.py → SyntaxError → 语言文件没生成。)
|
||||
pick_python() {
|
||||
local c
|
||||
for c in "$(command -v python3 2>/dev/null)" /usr/local/bin/python3 /usr/bin/python3 "${HOME}/.local/bin/python3"; do
|
||||
[[ -n ${c} && -x ${c} ]] || continue
|
||||
if "${c}" -c 'import sys; raise SystemExit(0 if sys.version_info >= (3, 7) else 1)' 2>/dev/null; then
|
||||
printf '%s' "${c}"
|
||||
return 0
|
||||
fi
|
||||
done
|
||||
return 1
|
||||
}
|
||||
PY="$(pick_python)" || {
|
||||
echo "[auto-deploy] 找不到 >= 3.7 的 python3, 中止"
|
||||
exit 1
|
||||
}
|
||||
echo "[auto-deploy] python3: ${PY} ($("${PY}" -V 2>&1))"
|
||||
|
||||
mkdir -p "${STATE_DIR}"
|
||||
TARGET="${1:-$(git -C "${REPO_DIR}" rev-parse HEAD)}"
|
||||
PREV="$(cat "${STATE_FILE}" 2>/dev/null || true)"
|
||||
|
||||
# job 容器里是 root, 会把 clone 里新生成的文件留成 root 所有, 影响宿主上的手工 git 操作。
|
||||
# 结束时(无论成功失败)把所有权还回去。
|
||||
restore_owner() {
|
||||
[[ "$(id -u)" == 0 ]] || return 0
|
||||
chown -R "${DEPLOY_OWNER_UID:-1001}:${DEPLOY_OWNER_GID:-1001}" "${REPO_DIR}" 2>/dev/null || true
|
||||
}
|
||||
trap restore_owner EXIT
|
||||
|
||||
# workflow 的 concurrency 之外再加一道, 防止手工执行与 CI 撞车
|
||||
exec 9>"${STATE_DIR}/lock"
|
||||
flock -n 9 || {
|
||||
echo "[auto-deploy] 已有部署在跑, 本次退出"
|
||||
exit 0
|
||||
}
|
||||
|
||||
echo "[auto-deploy] 目标 ${TARGET} (上次成功部署: ${PREV:-无})"
|
||||
cd "${REPO_DIR}"
|
||||
|
||||
# customization/custom/ 的指纹: 模板、静态页、生成的语言文件都在里面。
|
||||
# 这些是 Gitea 启动时加载的, 变了必须重启容器才生效(README §3), 而 `compose up -d`
|
||||
# 只在 compose 配置变化时才重建 —— 所以这里自己比指纹, 变了就 restart。
|
||||
custom_hash() {
|
||||
(cd customization/custom && find . -type f -exec sha256sum {} + | sort | sha256sum | cut -d' ' -f1)
|
||||
}
|
||||
|
||||
# compose 的 bind mount 源目录必须先存在【且属于当前用户】: 源目录不存在时 docker 会
|
||||
# 以 root 创建它, 之后 build.py 就写不进去(全新克隆第一次部署时真实踩到, 于是语言文件
|
||||
# 生成失败、「工单」回来了)。仓库里 custom/options/.gitkeep 从结构上避免这一点,
|
||||
# 这里再兜底检查一次, 失败就说清楚怎么办。
|
||||
prepare_custom_dirs() {
|
||||
local d
|
||||
for d in options public templates; do
|
||||
if [[ ! -d customization/custom/${d} ]]; then
|
||||
mkdir -p "customization/custom/${d}" 2>/dev/null || {
|
||||
echo "[auto-deploy] 无法创建 customization/custom/${d}" >&2
|
||||
return 1
|
||||
}
|
||||
fi
|
||||
if [[ ! -w customization/custom/${d} ]]; then
|
||||
echo "[auto-deploy] customization/custom/${d} 不可写 —— 很可能是 docker 以 root 创建过它。" >&2
|
||||
echo " 删除后重试(宿主上需 sudo; job 容器里是 root): rm -rf customization/custom/${d}" >&2
|
||||
return 1
|
||||
fi
|
||||
done
|
||||
}
|
||||
|
||||
deploy() {
|
||||
local before after
|
||||
prepare_custom_dirs || return 1
|
||||
before="$(custom_hash)"
|
||||
"${PY}" customization/build.py || return 1 # 生成语言文件 + 规范 custom/ 权限
|
||||
"${PY}" customization/build.py --check || return 1 # 生成物/权限校验, 不过就中止, 不碰容器
|
||||
after="$(custom_hash)"
|
||||
(cd deploy && docker compose up -d) || return 1 # 幂等: 只有配置/挂载/镜像变化时才重建
|
||||
if [[ ${before} != "${after}" ]]; then
|
||||
echo "[auto-deploy] custom/ 有变化(模板/静态页/语言文件), 重启 gitea 使其生效"
|
||||
(cd deploy && docker compose restart gitea) || return 1
|
||||
fi
|
||||
}
|
||||
|
||||
verify() {
|
||||
(cd deploy && ./scripts/verify.sh) || return 1 # 容器健康 + 本机 API + 经 Apache 反代
|
||||
if [[ -x ${REPO_DIR}/customization/check.sh ]]; then
|
||||
"${REPO_DIR}/customization/check.sh" "${PUBLIC_URL}" || return 1 # 定制断言
|
||||
else
|
||||
# 回滚到旧版本时那个版本可能还没有这个脚本 —— 那不是失败
|
||||
echo "[auto-deploy] (${TARGET} 这个版本没有 customization/check.sh, 跳过定制断言)"
|
||||
fi
|
||||
}
|
||||
|
||||
rollback() {
|
||||
if [[ -z ${PREV} ]]; then
|
||||
echo "[auto-deploy] 没有历史成功版本可回退, 保持现状"
|
||||
return 0
|
||||
fi
|
||||
echo "[auto-deploy] 回滚到 ${PREV}"
|
||||
# -f: 旧版本里可能没有 deploy/runner/* 这类文件, 它们在新版本是"未跟踪文件",
|
||||
# 会挡住普通 checkout(实测), 这里直接覆盖
|
||||
git checkout -f --detach "${PREV}"
|
||||
deploy || true
|
||||
verify || true
|
||||
}
|
||||
|
||||
# 包成一个函数再放进 if: 避免依赖 "&& 列表最后一个命令在 if 条件里是否触发 errexit" 这类细节
|
||||
pipeline() { deploy && verify; }
|
||||
|
||||
if pipeline; then
|
||||
echo "${TARGET}" >"${STATE_FILE}"
|
||||
echo "[auto-deploy] ✅ 部署成功 ${TARGET}"
|
||||
else
|
||||
echo "[auto-deploy] ❌ 部署或验证失败, 开始回滚"
|
||||
rollback
|
||||
exit 1
|
||||
fi
|
||||
Reference in New Issue
Block a user