ServerKit is a lightweight, modern server control panel for managing web applications, databases, and services on your VPS or dedicated server. Built with Python/Flask backend and React frontend.
Python astracloudflarecontrol-panelcyberpaneldnsfablehosting-control-panelhosting-panelkimi-k3server-managementserverkitubuntu-web-panelwebserver
docs(wordpress): assess + defer the XL/infra-blocked tail (#32/#33/#34)
Juan Denis98ffb5096eff
diff --git a/docs/WORDPRESS_ROADMAP.md b/docs/WORDPRESS_ROADMAP.mdindex d55805e4..82887a77 100644--- a/docs/WORDPRESS_ROADMAP.md+++ b/docs/WORDPRESS_ROADMAP.md@@ -284,23 +284,26 @@ Highest-effort, broadest surface — but by now the `WordPressSite` is a first-c- **Done when:** A promote can move just selected files/tables.- **Landed:** `PromoteModal` already had **files-only** (`code` type), **db-only** (`database` type), and **specific-folders** (the `include_plugins`/`themes`/`mu_plugins`/`uploads` checkboxes); the only missing piece was **specific-tables**, now added as two comma-separated inputs in the database section — **Exclude tables** (omitted entirely) and **Truncate tables** (structure promoted, rows dropped) — split into arrays on submit. The full backend chain already honored them (`POST …/promote` documents+forwards `config.exclude_tables`/`truncate_tables` → `promote_database`/`promote_full` → `clone_options` → `_transform_dump`), so this is pure UI wiring with no backend change. Verified: frontend lint-clean + production build.-### #32 — Per-site SFTP `[M]` ❌+### #32 — Per-site SFTP `[M]` ❌ — ⏸️ Deferred (Docker-correct path is a per-site SFTP **sidecar**, but it ships an unverifiable, publicly-exposed file-access surface)- **Today:** FTP is host-global (`ftp_service`); no per-site SFTP.- **Do:** Add SFTP via an sshd `Subsystem`/chroot scoped to the site root, bound to the site object.- **Reuse:** `ftp_service` patterns.- **Done when:** Each site exposes scoped SFTP credentials.+- **Assessment / why deferred:** The roadmap's host-sshd-chroot approach doesn't fit the Docker model — a managed site's files live in the `wordpress_html` **named volume**, not a host path, so a host-level chroot would target the wrong place. The **Docker-correct** design is a per-site **SFTP sidecar container** (e.g. `atmoz/sftp`) mounting `wordpress_html`, injected into the compose stack exactly like #23's redis (`_ensure_*_in_stack` + additive `compose up -d`), with a generated credential surfaced once and a new mapped port (via the template's port-allocation). That is genuinely implementable on the proven pattern — but it (a) opens a **publicly-exposed, security-sensitive file-access surface** that should be firewalled and that I cannot runtime-verify from the dev host, and (b) consumes a port + a container per site. Shipping security-sensitive infra blind violates the quality bar, so this is deferred for a focused pass on a real Docker host (where the sidecar, chroot perms, and firewall can be exercised). No code shipped.-### #33 — Agency scale (workspaces, RBAC, white-label, reports) `[XL]` 🟡+### #33 — Agency scale (workspaces, RBAC, white-label, reports) `[XL]` 🟡 — ⏸️ Deferred (XL epic — split into its own milestone; touches cross-cutting models + RBAC + reports)- **Today:** No `workspace_id` FK on `Application`/`WordPressSite`/`Server`; permissions are global with no per-site ACL; white-label lives in `localStorage` and never reads `Workspace.logo_url`/`primary_color`.- **Do:** Add `workspace_id` FKs + per-site ACL rows + environment-tier RBAC in promote/sync/bulk endpoints; server-side branding scoped to workspace; monthly client reports aggregating uptime/updates/backups/security.- **Reuse:** `workspace_service`, `permission_service`, `audit_service`.- **Done when:** A site/environment can be scoped to a workspace with per-site roles and branded reports.+- **Assessment / why deferred:** A genuine **`XL`** multi-day epic (the roadmap's own guidance is "split before starting"), and it cuts across the whole system rather than the WordPress object: (1) `workspace_id` FK migrations on `Application`/`WordPressSite`/`Server` + backfill + scoping *every* list/query; (2) a per-site **ACL** model + enforcement woven through promote/sync/bulk endpoints; (3) moving white-label from `localStorage` to server-rendered, workspace-scoped branding; (4) a monthly **reports** generator aggregating the now-existing uptime (#26) / updates (#29) / backups / security (#28/#30) signals. Each sub-part is its own feature; done together they're a milestone, not a single change — and the cross-cutting FK + RBAC rework is high-blast-radius. **Foundation now in place from this session:** the report's data sources (per-site uptime/incidents #26, update history #29, vuln findings #28) all exist, so the reports sub-feature is the most self-contained slice to start with. Deferred to a dedicated milestone. No code shipped.-### #34 — Horizontal scaling `[XL]` ❌+### #34 — Horizontal scaling `[XL]` ❌ — ⏸️ Deferred (XL + blocked on the same per-site reverse-proxy/upstream layer as #21)- **Today:** `nginx_advanced_service` has load-balancing primitives (round-robin/least-conn/IP-hash) but WP containers are stateful (local uploads, no shared object cache).- **Do:** Make WP stateless — shared media (uploads on a shared volume or S3 offload), shared Redis object cache (#23), then nginx `upstream` load balancing across replicas with sticky handling where needed.- **Reuse:** `nginx_advanced_service`, #23, `storage_provider_service`.- **Done when:** A site can run N replicas behind a balancer with consistent media + cache.+- **Assessment / why deferred:** **`XL`** *and* infra-blocked. Managed sites are single `wordpress:*-apache` containers published directly on `localhost:PORT` with **no per-site nginx in front** — the very reverse-proxy layer #34's `upstream` load-balancing needs, and the same missing infra that blocks **#21** (preview URLs) and that #8's backend/#25's "nginx" premise also ran into. Beyond the balancer, making WP **stateless** is itself a large build: shared media (an S3/offload plugin or a shared uploads volume across replicas, via `storage_provider_service`), a shared Redis object cache (the **#23** redis sidecar exists but is per-site, not shared across replicas), and replica orchestration in the compose stack. So #34 needs (a) the per-site reverse-proxy/routing layer to exist first (a prerequisite shared with #21), then (b) a stateless-WP refactor, then (c) the `upstream` wiring — a milestone-sized effort gated on infrastructure not yet built. Deferred. No code shipped.### #35 — WordPress workflow nodes, events & CLI `[L]` 🟡 — ✅ Done (WP lifecycle events emitted + subscribable; workflow action-nodes + CLI deferred)- **Today:** The event/webhook + workflow engine can't see a `WordPressSite` — `EVENT_CATALOG` has no WP lifecycle events, WP operations emit nothing, the workflow builder has no WP node types, and there's no `serverkit wp` CLI.