Conversation
CI (.github/workflows/ci.yml), on every PR and push to main: - check: npm ci, lint, UI tests, build, server tests - docker: build the image, start it, smoke /healthz, /, /docs (200) and /api/skills (401 without login) CD (deploy/cd/ash-cd.sh + systemd user timer, every 2 min): - deploys main only when its "check" and "docker" runs succeeded - backup DB + skills_files, git archive from its own mirror, build ash:<sha>, derive compose by swapping only the image tag, switch - smoke: /healthz, /, /docs 200, /api/skills 401, skill count unchanged, no migration/uncaught errors in logs; public /healthz only warns - automatic rollback on smoke failure; failed commits are never retried - reports to GitHub Deployments (production); keeps the last 10 images - manual: ash-cd status | deploy <sha> [--force] | rollback [<tag>] - pull-based on purpose: the repo is public, so no self-hosted runner Rehearsed end to end on a staging container with a copy of production data: deploy, smoke-failure rollback, manual rollback, poll-waits-for-CI. docs/deploy.md: CI/CD is now the standard path; the manual five steps remain as the fallback. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
What
.github/workflows/ci.yml): every PR and push tomainrunscheck(lint, UI tests, build, server tests) anddocker(build image, start it, smoke/healthz,/,/docs= 200 and/api/skills= 401).deploy/cd/): a systemd user timer on seed-SER9 pollsmainevery 2 minutes and deploys only commits whosecheckanddockerruns succeeded — backup → buildash:<sha>→ swap compose image tag → smoke → automatic rollback on failure. Status is reported to GitHub Deployments (production).docs/deploy.md: CI/CD becomes the standard path; the manual five steps stay as the fallback.Why pull-based
The repo is public, so a self-hosted runner on the production host would let fork PRs run code there. The host only pulls and only deploys CI-green
main.Verified
Rehearsed on a staging container (
ash-staging, port 19555) with a copy of production data:/api/skills≠ 401 and rolled back automaticallyash-cd rollbackandash-cd poll(waits while CI is pending)Production was not touched.
🤖 Generated with Claude Code