SHA256
forked from course-team/tjhlp-gitea
feat(ci): 落地 main 自动部署的可复用件(runner 配置/部署脚本/定制断言/工作流)
按 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:
@@ -17,6 +17,10 @@ credentials_*.csv
|
||||
# Deployment (docker compose)
|
||||
deploy/.env
|
||||
deploy/backups/
|
||||
# CI/CD: 部署状态(上次成功的 SHA)与 runner 的注册凭据/缓存
|
||||
deploy/.state/
|
||||
deploy/runner/.env
|
||||
deploy/runner/data/
|
||||
|
||||
# Customization
|
||||
customization/custom/options/locale/locale_zh-CN.json
|
||||
|
||||
Reference in New Issue
Block a user