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(roadmap): bring Recently Completed current through the convergence run
Juan Denised77f169c567
diff --git a/ROADMAP.md b/ROADMAP.mdindex bbdb5d9a..de0ecceb 100644--- a/ROADMAP.md+++ b/ROADMAP.md@@ -10,6 +10,11 @@ This document outlines the development roadmap for ServerKit. Features are organ### Recently Completed (v1.7.x)+- **Managed Databases Join the Recycle Bin** - Deleting a managed database no longer destroys it on the spot. Like applications before it, a deleted database now lands in the Recycle Bin with its content and backup policy intact and restorable; only an explicit purge (or asking for the data to be dropped at delete time) is destructive. The distinction that matters: delete keeps your data, purge is the irreversible step, and the UI says which one you are about to do.+- **One Error Shape, With a Request ID You Can Quote** - Every API error now comes back in one consistent JSON envelope carrying a request correlation id, so "it failed" in a bug report can be matched to the exact request in the panel's error monitor. Behind that, crashes a route used to catch and quietly convert into a vague 200 or a bare 500 — the PR-webhook receiver, the job queue bus, and several others — are now recorded in the error monitor every time, with tests pinning that a swallowed crash is a bug, not a behavior.+- **Live Streams and Polling That Behave** - Panel pages pause their background polling when the tab is hidden and catch up the moment you return, so an idle dashboard tab stops costing server load and laptop battery. Live output (deploys today, more run kinds on the same rails next) streams through one event scheme with a shared room grammar, and the deploy console keeps working unchanged through the transition.+- **Remote-Access Tunnels Reconcile on Every Transport** - Tunnel reconciliation used to fire only for agents connected over WebSocket; an agent on the HTTP long-poll fallback missed it. Both transports now go through the same door, so a NAT'd box behind a strict proxy gets the same tunnel repair behavior as everyone else.+- **Credential Encryption Failures Are No Longer Silent** - A failure to encrypt stored server credentials used to keep the old value without telling anyone. It now surfaces as an error, so a misconfigured encryption key is something you find out about at save time, not at the next incident.- **Run It Behind Your Own Reverse Proxy** - Already running Caddy, Traefik or Nginx Proxy Manager, with Let's Encrypt or a private CA of your own? That is now a supported, documented and tested way to run the panel rather than something you reverse-engineer from the install script. Two topologies are written up — keep ServerKit's nginx (full features, host install) or point your proxy straight at the panel (panel only, the Docker shape) — with proxy config snippets, the two environment variables that matter, and a symptom-to-cause table for the redirect loop, the rejected websocket and the wrong client IPs. A new installer switch sets a box up this way in one line, and an install-config file makes the whole thing re-runnable. Tests now pin the properties an external proxy depends on: the panel emits no redirect to HTTPS from any of its 352 routes, the public URL is honoured as a websocket origin while strangers are rejected, and HSTS stays off when TLS is somebody else's job.- **Rate Limits and Audit Logs See the Real Visitor** - The panel is always served through its own nginx, so every request arrived carrying nginx's address rather than the visitor's — and the installer never turned on the setting that recovers the real one. Per-IP rate limiting, the login brute-force block and every audit-log entry were therefore keyed on a single local address, which quietly weakened all three: one abusive client shared a bucket with everyone else. New installs now enable it, and re-running the installer backfills it on existing ones without touching a value you set yourself. It deliberately stays off when the backend port is exposed directly, because a visitor who can reach it without passing through nginx can simply claim any address they like.- **Installing With a Domain No Longer Breaks nginx** - Setting a panel domain at install time wrote a bare-IP redirect that declared itself a second default server on port 80 — something nginx refuses outright, in both HTTP and HTTPS modes, so nginx would not start and the installer had no `nginx -t` to say why. The redirect now matches a bare IP by name pattern instead of competing for the default, verified against real nginx, with a regression guard.