Add site:pull: migrate a WordPress (or any) site between remote hosts

[nbejansen]

What

Replaces the original wp:pull (which mirrored a remote site onto the box running the tool) with site:pull, run from an admin's machine to migrate a site from a source host to a destination host.

# pilot.yml
sites:
  example:
    url: https://example.com
    host: web124.sitepilot.net
    user: bob
    path: ~/httpdocs
    source:
      host: 1.2.3.4
      user: alice
      path: /var/www/example

site:pull example        # or `site:pull` to pick interactively

How it works

• Site selection — sites: map keyed by name; pick by argument or interactive picker.
• WordPress detection — by wp-config.php on the source. WordPress → files and database; anything else → files only (works for non-WP apps too).
• Direct transfers — rsync runs on the destination, pulling from the source over SSH agent forwarding; the file sync and DB dump never pass through the admin machine.
• No WP-CLI required on the source — uses the source's own wp if present, otherwise pulls a fresh wp-cli.phar into a per-run temp dir; source commands run with --allow-root.
• Credentials preserved — the destination keeps its own wp-config.php (valid DB creds/salts); only the table prefix is reconciled to the source's so the import resolves.
• DB flow — export on source → destination pulls the dump → wp db import on destination → table-prefix reconcile → search-replace the URL → wp db optimize (always, as the final DB step, to reclaim space and refresh index statistics).
• Output — Laravel Prompts: select/confirm, a progress bar with a live current-step hint, and a final summary of what was done. SSH uses BatchMode + ConnectTimeout.

Structure

Remote (one host), Migration (a site's source/destination/url + validation rules), Ssh, Rsync, WpCli (destination WP-CLI), RemoteWpCli (source WP-CLI, provisioned on demand).

Tests

Full Pest coverage (72 tests) with Process::fake. phpunit runs as APP_ENV=testing so Laravel Prompts use their console fallbacks, letting expectsChoice/expectsConfirmation drive select/confirm.

Operational notes

• The admin SSHes to the destination with their agent forwarded (-A); the destination uses that key to reach the source — so the admin's key must be authorized on both.
• Pulling a fresh wp-cli.phar needs outbound internet on the source (only when it has no wp).
• Source & destination should share a table prefix convention, or rely on the automatic reconcile.