WP Manifestindependent plugin directory
manifest / integrations / taw-hub-companion

TAW Hub Companion

Signed wp-json/taw-hub/v1 receiver for the TAW Site Manager control hub (companion plugin, taw-site-manager ADR-0003).

by Marco Del Riego · github.com/relmaur/taw-hub-companion

1stars
2release downloads
0forks

Install

The author publishes release zips, so WP-CLI can install straight from GitHub:

wp plugin install https://github.com/relmaur/taw-hub-companion/releases/download/v0.2.0/taw-hub-companion-0.2.0.zip

Declares an update source (https://github.com/Relmaur/taw-hub-companion), so updates arrive through the plugin's own updater.

From the readme

TAW Hub Companion The signed wp-json/taw-hub/v1/ receiver a TAW-framework WordPress site exposes to the TAW Hub control hub. No passwords — every request is verified against the Hub's Ed25519 key per the Hub's ADR-0003 wire protocol. Plugin architecture: ADR-0005. Was briefly TAW\Hub inside taw/core v1.20.0. That was the wrong home (theme framework ≠ fleet-management control plane) and the wrong protocol (independently invented, not ADR-0003). Reverted in taw/core v1.20.1; rebuilt here. Install 1. Drop the plugin in wp-content/plugins/taw-hub-companion/ and run composer install (or ship the built plugin with vendor/ included). 2. Define these in wp-config.php (never the options table): 3. Activate. The plugin generates this site's own Ed25519 keypair. 4. Register the site with the Hub — on a TAW site, php bin/taw hub:enroll (taw/core ≥ v1.23.0) does it in one command. Otherwise GET /wp-json/taw-hub/v1/health returns sitepublickey + sitekeyid (also shown in an admin notice); give those to the Hub operator (RegisterSite). Without TAWHUBPUBLICKEY the plugin is inert — every route returns 501 and an admin notice explains what to define. Updating The plugin s

Read the full README on GitHub →

Releases

TagPublishedAssetDownloads
v0.2.0 Sep 3, 2026 taw-hub-companion-0.2.0.zip 2