Quick Start
Start with a dry-run profile and SSH aliases that already work from the machine running HostShift.
ssh old-server truessh new-server trueRun the first discovery and plan:
hostshift doctor --source old-server --target new-server --jsonhostshift discover --source old-server --name rehearsal --profile rehearsal.profile.yaml --jsonhostshift plan --profile rehearsal.profile.yaml --target new-server --jsonhostshift explain --profile rehearsal.profile.yaml --target new-server --jsonRun dry-run phases:
hostshift prepare --profile rehearsal.profile.yaml --target new-server --jsonhostshift sync --profile rehearsal.profile.yaml --target new-server --jsonhostshift verify --profile rehearsal.profile.yaml --target new-server --jsonApply Discipline
Section titled “Apply Discipline”Only use --apply after:
- the profile is reviewed and approved
- blockers are resolved
- target-side writes are expected
- database credentials are supplied through environment variables
- rollback notes are understood
hostshift prepare --profile rehearsal.profile.yaml --target new-server --apply --jsonhostshift sync --profile rehearsal.profile.yaml --target new-server --apply --jsonhostshift verify --profile rehearsal.profile.yaml --target new-server --apply --jsonThe source server remains read-only in both dry-run and apply modes.