-
Notifications
You must be signed in to change notification settings - Fork 0
Getting Started
Fleet has two roles:
- The hub is the WordPress site where you install OpenStation and Fleet for OpenStation.
- A managed site is any other WordPress site that approves the hub's connection.
The managed sites stay independent. They keep their own hosting, database, users, permissions, plugins, and content. They do not need to belong to a WordPress Multisite network.
| Fleet hub | Managed site | |
|---|---|---|
| WordPress | 6.5 or newer | 6.0 or newer |
| PHP | 7.4 or newer | Whatever the installed OpenStation release requires |
| HTTPS | Required | Required |
| Plugins before connection | OpenStation and Fleet | None |
| Access | Administrator | An account allowed to perform the work Fleet should do |
Both sites must be publicly reachable over HTTPS. Fleet deliberately keeps WordPress's safe HTTP boundary and does not connect to private-network or loopback production targets.
- Download
fleet-for-openstation.zipfrom the latest release. - Install and activate OpenStation on the hub.
- Go to Plugins → Add New Plugin → Upload Plugin.
- Upload the Fleet ZIP and activate it.
- Open Fleet from wp-admin or the OpenStation desktop.
- Enter the managed site's full HTTPS address, such as
https://client.example. - Select Continue on site.
- Sign in to that WordPress site if it asks.
- Review WordPress's native connection request and approve it.
- Fleet returns to a visible setup screen while WordPress installs or activates OpenStation.
- Select Manage when the site is ready.
Fleet never asks you to type a normal WordPress password into Fleet. A login screen belongs to the managed WordPress site and appears only when you are not already signed in there.
WordPress generates a separate Application Password for Fleet. It is not the approving user's normal sign-in password. Fleet stores it encrypted on the hub and sends it only to that site's HTTPS REST API.
The connection inherits the approving account's WordPress permissions. Connect with an administrator when Fleet should manage the whole site. Use a less-privileged account only when you intentionally want a smaller management surface.
The credential appears under Users → Profile → Application Passwords on the managed site as Fleet for OpenStation on hub-domain. Revoking it does not change the user's normal password.
Fleet keeps the working WordPress connection and shows Finish OpenStation setup on the site card. Fix the hosting or filesystem problem, then retry without approving another connection.
Common blockers include missing plugin-install capabilities, a read-only plugins directory, interactive FTP or SSH requirements, WordPress.org being blocked, or a host policy that prevents REST-based plugin installation.
Entering an already-connected URL focuses the existing workspace instead of creating another credential. Opening the same site again also returns to its persistent OpenStation window rather than duplicating it.
Select Disconnect for a site. Fleet first deletes the exact Application Password it created, then removes the local site record. If the remote site cannot confirm revocation, Fleet keeps the record so you can retry.
Disconnect every site before uninstalling Fleet. A removed hub plugin cannot reliably contact its former managed sites. If Fleet was already removed, revoke any remaining Fleet credential from the approving user's profile on each managed site.
Next: Managing sites · Troubleshooting · Security