Sites

A site is a WordPress folder on a server (or on this computer). The app needs the folder and the way in; it finds the rest.

Adding a site

Sites, then Add site.

• Server — pick one you added, or Enter the details myself for host, user, port and key by hand.
• Name — lowercase letters, digits, hyphens. This is what appears in the list and in backup names.
• Root — the folder that holds wp-config.php. Type it if you know it; otherwise Find WordPress… looks in the usual places on that server and lists what it finds.
• Test connection — checks SSH, that the folder is a WordPress install, and the tools on the server. Read its result before saving; it names anything missing.

The site list

Each row shows the name, host, a fourteen-day strip of backups (green = backed up that day, red = a failed attempt, grey = nothing), when it was last backed up, and whether it has a schedule (Auto). Hover a row for Back up and Migrate; the ⋯ menu has everything else, including pinning a site to the top of the list.

Sort by name, oldest backup first, or most storage first. Tick several rows to Back up selected or Update selected in one go.

Scanning

Opening a site shows its overview. Scan site reads the WordPress and PHP versions, pending updates and user counts over WP-CLI. Scanning is optional; backups do not depend on it. If WordPress on the site is throwing a fatal error, the scan still lands — the app retries with plugins and themes disabled — and the overview says so, naming the plugin.

Local sites

A site with no host is local: its root is a folder on this computer. New local site creates one in Docker with WordPress installed, ready to try the app against; it needs Docker Desktop running.

Removing a site

Remove in the site header takes the site out of the list. Its backups stay on disk. For a local Docker site, you can also remove the containers and files.