Changelog¶

0.3.1¶

Added explicit 90-day telemetry enable/disable controls to the Updates page.
Added the minimal self-hosted telemetry receiver, retention cleanup and local report.
Expanded the privacy notice with payload, retention and revocation details.

Removed HTTP Basic Auth while retaining optional, default-on port-knocking.
Made SpawnWP passkey or password + TOTP authentication the sole cockpit login.
Clarified first enrollment with explicit steps, authenticator examples and copyable TOTP/recovery material.
Replaced ambiguous fallback-password terminology and expanded the installer's first-time activation instructions.
Added Nginx rate limiting to authentication ceremonies.
Added an idempotent host migration that validates Nginx before removing Basic Auth state.

All notable changes to this project are documented here. The format is based on Keep a Changelog, and the project aims to follow Semantic Versioning.

Cockpit static assets can be resolved in isolated validation environments while the production default remains /srv/wp-cockpit/static.

One-command Ubuntu/Debian installer with signed releases, TLS, primary environment provisioning and a root-only credentials report.
Mandatory passkey login with password + TOTP fallback, recovery codes, server-side sessions, CSRF protection and root recovery.
Optional port knocking and separate 90-day telemetry consent.

Update and rollback health checks now wait for the cockpit HTTP endpoint instead of treating an early systemd active state as application readiness.

First public release.

Signed GitHub Release updater with explicit update checks, transactional activation and rollback; existing WordPress environments remain untouched.
Initial public documentation (MkDocs + Material).
Web cockpit: spawn, start/stop/restart, snapshot/restore, destroy sites; live metrics; PHP-version switching; one-click Adminer and Mailpit.
Two-domain architecture: WordPress content on DOMAIN, knock-protected cockpit and admin tools on COCKPIT_DOMAIN, on a single SAN TLS certificate.
Built-in WordPress.org QA toolchain: Plugin Check, Theme Check, PHP_CodeSniffer (WPCS) + PHPCompatibilityWP, PHPStan + WP stubs, Query Monitor, WP Crontrol, User Switching; per-site Mailpit.
Security defaults: port-knocking with sliding sessions, HTTP Basic Auth, automatic HTTPS, dropped Linux capabilities, no Docker socket exposure, loopback-only service ports, per-install random secrets.