docs: one deploy verb — deploy targets wherever the stack lives
`deploy` now resolves its target from the stack's topology and `release` is an
alias for `deploy --require-remote` (strut#415). The wiki taught the opposite
rule — Deployment.md literally advised "use release for VPS deployments, not
deploy" — so the framing is inverted throughout.
- Deployment: rewrite the opening, add "Where a Deploy Lands", document the
alias and the compatibility promise, --require-remote, and the pipeline skip
flags (--no-sync / --no-migrate / --no-rollback / --backup-first / --strict).
- GitHub-Action: `deploy` is the primary CI command and the action passes
--require-remote. Drop the "deploy has an interactive prompt and will hang a
hosted runner" guidance — the prompt no longer exists. Replace the "deploy
hangs in CI" entry with the failure that can actually bite now: a deploy that
silently targeted the runner.
- MCP-Server: strut_deploy runs deploy --require-remote and never falls back
to a local deploy.
- Sweep command examples across the wiki; leave `lock release` alone.
docs: update wiki for v0.29.0 — fleet sync, hooks, data safety, upgrade
docs: fix CLI inaccuracies and sync to v0.28.0
- Version badges → 0.28.0 (Home, _Footer); Multi-Host 'since' → v0.22.0
- CLI-Reference: correct audit:diff signature (<host> [user] [key] [port])
- Deployment: logs --tail 50 → --since 30m (no --tail flag exists)
- Configuration + Volume-Management: volume.conf is shell vars + VOLUME_OWNERS, not colon rows
- Key-Rotation: ssh:keygen stores in ~/.ssh/strut_<host>_*; ci:init also supports gitlab/manual
- Database-Backups: backup cleanup → backup retention enforce
- Data-Anonymization: hash uses HEX() on SQLite (no SHA256)
- Local-Development: local env file is stacks/<stack>/.env.local
- Agent-Steering: add development-workflow.md steering file
- VPS-Audit-and-Migration: fix reversed audit key/port args
- Monitoring: remove nonexistent flags/commands (--env/--vps, reload/update/restart/backup, alert-route, webhook --method); correct env-file reference
- Domain-and-SSL: document Caddy reverse-proxy backend (automatic HTTPS)
docs: add Multi-Host Topology page, BUILD_MODE docs, rebuild command
Document v0.20.0: blue-green deploy mode
New Blue-Green-Deploy page covers opt-in via DEPLOY_MODE=blue-green or
--blue-green flag, the 9-step orchestration flow, the .bluegreen state
file, tunables (BLUE_GREEN_HEALTH_TIMEOUT / BLUE_GREEN_DRAIN), compose
file requirements (no container_name, no port collisions), proxy hook
contract with shared-nginx and Caddy admin-API examples, fast
state-file rollback, timeout tuning guidance, and common failure modes.
CLI-Reference notes the new --blue-green/--standard flags and
blue-green rollback behavior. Configuration gains the new strut.conf
keys. Deployment links out to the new page, Home and Sidebar list it.
Update wiki for v0.8.0: doctor, pre-deploy hooks, config
Update wiki for v0.7.0: rollback, validate, dry-run, anonymization, reverse proxy
docs: comprehensive wiki for strut CLI
20 pages covering:
- Getting Started (Installation, Quick Start)
- Core Concepts (Architecture, Configuration, CLI Reference)
- Operations (Deployment, Backups, Key Rotation, Drift, Domain/SSL, Monitoring, Volumes)
- Advanced (VPS Audit/Migration, Stack Validation, Debugging, Local Dev)
- Contributing (Conventions, Adding Commands, Project Structure)
- Sidebar navigation and footer