Commit Graph
7 Commits
Author SHA1 Message Date
bot-hermes 8975aeb870 fix(deploy): atomic deploys — build in builds/<sha-stamp>, verify fresh dist, swap, health-check + auto-rollback
- Stage to timestamped builds/ dir; live custom-build untouched during install+build
- Verify dist exists, non-empty, newer than stage start (stale/partial fails)
- Symlink swap stays single atomic op; previous target saved for rollback
- Post-restart health-check on / (24x5s); on failure flip back, restart, notify, exit 1
- Prune to 2 newest builds on success; notify on failure (if: failure())
- Root cause: rm -rf custom-build destroyed the live dir mid-deploy; UI 404'd until build finished
2026-09-07 17:48:29 -04:00
coder-ops 3991a6432a fix(deploy): route deploy clone to BuzzbeeSCD/openchamber (Vibing repo removed) 2026-09-06 11:13:19 +00:00
bot-hermes f9fc8aa680 ci(deploy): notify on successful deploy only (moved from push webhook) 2026-09-05 20:42:43 +00:00
bot-hermes b3c24935c0 ci(deploy): use SSH URL for checkout clone
The https://gitea@giteassh.buzzbee.dev:Vibing/... URL parsed the colon as a
port. Use the SSH form gitea@giteassh.buzzbee.dev:Vibing/openchamber.git
which the runner's deploy key authenticates.
2026-09-05 09:00:04 -04:00
bot-hermes cd6b24d9b0 ci(deploy): clone into subdir, don't rm the runner cwd
rm -rf $GITHUB_WORKSPACE deleted the runner's own working directory,
breaking git clone (fatal: Unable to read current working directory).
Clone into $GITHUB_WORKSPACE/repo instead.
2026-09-05 08:58:53 -04:00
bot-hermes 75e81211ea ci(deploy): add checkout step to deploy workflow
The workflow assumed $GITHUB_WORKSPACE was already a git repo, but the
host-mode runner doesn't auto-checkout. Added an explicit clone step using
the runner's deploy key (gitea@giteassh.buzzbee.dev).
2026-09-05 08:57:27 -04:00
bot-hermes e67987533e ci: add deploy workflow for custom branch (OpenChamber-CUSTOM) 2026-09-03 11:36:34 +00:00