windy/vps

Files

T

windyboy b0c01b2551 docs(runbooks): add runbook spec, template, index and 6 first-batch runbooks; light-enhance existing 10

- RUNBOOKS.md: repo-level spec (six-field model, naming, safety, maturity path)
- runbooks/_template.md + README.md: standard template and 16-entry routing index
- new: issue-to-merge, fix-ci, release, rollback, network-change, network-recovery
- light-enhance 10 existing runbooks with Purpose/Scope/Safety headers
- AGENTS.md: point step 3 at index/spec, add runbook execution rules
- docs/agent-runbook-guide.md: archive of Manus AI guide

2026-08-17 15:59:46 +08:00

2.3 KiB

Raw Blame History

Runbook: mailcow update (mx2)

Purpose

Update the mailcow stack on mx2 to the latest supported release.

Scope

Applicable: mx2.windy.me, /opt/mail.
Not applicable: config changes beyond the update, DB migration, secret rotation.

Approval gates

Action	Risk	Explicit approval
Run `./update.sh` (recreates containers, brief mail interruption)	Medium	Yes — user confirmation required

Target: mx2.windy.me
Path: /opt/mail
Confirm with the user before running an update.

Safety

Never run the update without explicit user confirmation.
Never pass secrets into the chat log; do not commit mailcow.conf.
If a step fails, capture docker compose ps and logs and stop before further changes.

Before

Run mailcow-health (Ansible health report). Record baseline.
Note config quirks in mailcow.conf, especially:
- SKIP_CLAMD=y — after update, clamd may still be running until services are recreated per mailcow docs.
- SKIP_LETS_ENCRYPT, ports, hostname — should stay mx2.windy.me.
Disk/memory: df -h / and free -h on the host.

Update

ssh -t windy@mx2.windy.me 'cd /opt/mail && ./update.sh'

Prefer interactive SSH (-t) so prompts work.
Do not pass secrets into the chat log; do not commit mailcow.conf.

If update asks to stop/recreate containers, allow it unless the user said otherwise.

After

Re-run health checks (mailcow-health).
Confirm UI: https://mx2.windy.me
Confirm SMTP banner and queue empty.

If SKIP_CLAMD=y but cow-clamd-mailcow-1 is still Up and that is unwanted:

cd ansible
ansible-playbook playbooks/compose-reconcile.yml --limit mailcow \
  -e '{"service_reconcile_confirm": true, "service_reconcile_targets": ["all"]}'

Only after user OK; recreate briefly interrupts mail.

Update Verified on hosts/mx2.windy.me.md with date and outcome.

Rollback

Mailcow updates are image/git based; there is no one-click rollback in this runbook. If something fails, capture docker compose ps and docker compose logs --tail=100 for the failing service and stop before further changes.

2.3 KiB Raw Blame History