Deploy — removed (breaking change)¶
The vibew deploy command was removed in the release referenced by
ADR-086. It has been replaced
by vibew bundle plus a manual scp / ssh / docker compose up -d flow.
Running vibew deploy today prints a deprecation message to stderr and
exits with code 2. No files are transferred, no SSH connection is opened,
and no remote state is touched.
What changed¶
| Before (removed) | After (supported) |
|---|---|
vibew deploy --target ssh://user@host --config vibewarden.prod.yaml |
vibew bundle + scp -r .vibewarden/bundle/ user@host:~/ + ssh user@host 'cd bundle && bash deploy.sh' |
vibew deploy status --target ssh://user@host |
ssh user@host 'cd ~/bundle && docker compose ps' |
vibew deploy logs --target ssh://user@host --lines 50 |
ssh user@host 'cd ~/bundle && docker compose logs --tail=50' |
vibew deploy --dry-run |
vibew bundle (bundle is always written locally; inspect .vibewarden/bundle/) |
Migration — three steps¶
See Bundle to VPS for the end-to-end walkthrough. In short:
# 1. Build the deployment artifact locally.
vibew bundle --output .vibewarden/bundle/
# 2. Copy the bundle to the remote host.
scp -r .vibewarden/bundle/ user@host:~/
# 3. Start the stack on the remote host.
ssh user@host 'cd ~/bundle && bash deploy.sh'
The bundle is self-contained and deterministic: same inputs, same bytes.
See vibew bundle for the flag reference.
Why the change¶
Four retrospectives converged on the same finding: vibew deploy's remote
SSH orchestration — rsync, remote docker compose, remote OpenBao bootstrap,
remote health probes, remote arch checks — was the single largest source of
bugs and user friction in the product (16 bugs across 3 retro cycles).
ADR-086 retires the feature in favour of a thin, purely local bundle
pipeline. The user owns the transport.
Rollback¶
This is a one-way change. The deploy stub exists for one release only and is
scheduled for removal in the release after that (tracked by issue #1063).
New scripts and agent prompts must target vibew bundle from day one.