vps-deploy

# VPS Deploy <!-- routing-eval reads this line; it lives in the BODY so the always-on skill LISTING stays inside Claude Code's budget (1% of the context window) — an overflowing listing gets descriptions truncated or dropped, which strips the very keywords a match depends on. --> Trigger phrases: "deploy", "push to the server", "install on the VPS", "ship it to the server", "go to production" A solid deploy has a single idea: **swap the running version with the new one in a reversible way.** That is, when you put the new version in place, don't throw the old one away — keep it aside. If the new version can't pass the health gate, undo the swap and no one notices. This skill builds the deploy around this swap; Docker or bare-metal, a single app or different runtimes, it makes no difference. > **Kit adaptation (local, .claude/):** Default backend is **.NET (Docker recommended)**. **Deploy requires explicit > approval (§4.4)**; a backup before every swap and a health gate after are mandatory. If `.deploy.yml` carries server > credentials it goes into `.gitignore`. §4 Prohibitions apply. ## Checklist - [ ] Runtime + deploy method determined - [ ] Config taken from `.deploy.yml`/the user, SSH verified - [ ] Reverse proxy + (if there is a domain) SSL in place - [ ] Running version backed up to `releases/` - [ ] User approved the deploy, new version deployed - [ ] Health gate passed (otherwise automatic rollback performed) - [ ] If requested, single-command scripts (`d...