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: how to run the panel behind your own reverse proxy
Juan Denis2624816680f5
diff --git a/AGENTS.md b/AGENTS.mdindex 11f890fe..0459f9f1 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -30,8 +30,8 @@ cd frontend && npm run buildcd backend && pytestcd backend && pytest --cov=app-# Docker-docker compose -f docker-compose.dev.yml up --build+# Docker (all-in-one panel container; no host management)+docker compose up -d --build```Default dev credentials: `admin` / `admin`diff --git a/CLAUDE.md b/CLAUDE.mdindex b103e7de..ad32b09d 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -30,8 +30,8 @@ cd frontend && npm run buildcd backend && pytestcd backend && pytest --cov=app-# Docker-docker compose -f docker-compose.dev.yml up --build+# Docker (all-in-one panel container; no host management)+docker compose up -d --build```Default dev credentials: `admin` / `admin`diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex fe508663..53470f7a 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -38,9 +38,14 @@ Open http://localhost:41921 — login: `admin` / `admin````bash./scripts/dev/dev.bat up # Windows-docker compose -f docker-compose.dev.yml up --build # Linux/Mac+docker compose up -d --build # Linux/Mac```+The compose stack runs the all-in-one panel container (`Dockerfile`) on+http://localhost:5000. It has no access to the host, so system-management+features (packages, firewall, systemd, host nginx) are unavailable — use+`./dev.sh` for those.+---## Quick Referencediff --git a/README.md b/README.mdindex d3345a98..e8a8f9d6 100644--- a/README.md+++ b/README.md@@ -86,9 +86,15 @@ or `--release [version]` for release tarballs.git clone https://github.com/jhd3197/ServerKit.gitcd ServerKitcp .env.example .env # then edit .env with your secrets-docker compose up -d # access at http://localhost+docker compose up -d # access at http://localhost:5000```+Runs the panel as a single container. Note a containerised panel **cannot manage+its own host** — no systemd, no host nginx, no managed site vhosts; use Option 1+for that. It ships without nginx and never redirects to HTTPS, which makes it the+right target to put your own reverse proxy in front of — see+[Running behind your own reverse proxy](docs/INSTALLATION.md#running-behind-your-own-reverse-proxy).+### Option 3: Manual InstallationSee the [Installation Guide](docs/INSTALLATION.md) for step-by-step instructions.diff --git a/ROADMAP.md b/ROADMAP.mdindex a78973e7..af344674 100644--- a/ROADMAP.md+++ b/ROADMAP.md@@ -10,6 +10,9 @@ This document outlines the development roadmap for ServerKit. Features are organ### Recently Completed (v1.7.x)+- **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.+- **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.+- **Docker Actually Runs the Panel** - `docker compose up -d` started nothing at all: every service had ended up behind an opt-in profile while the README and install guide still gave that command as the way to install with Docker. It now runs the real all-in-one panel on port 5000 with a persistent volume for the database. The image itself could not boot either — it wrote its database to a directory it never created — and the developer docs pointed at a compose file that has never existed. All corrected, with a guard so a profile change cannot silently empty the default command again.- **Uptime Monitors** - Monitoring is no longer only about the machine the panel runs on. A monitor watches anything you point it at — a website, an API endpoint, a database port, a mail server or a managed WordPress site — with HTTP, keyword, port, ping, DNS and SMTP checks, per-monitor intervals, expected status ranges, redirect and TLS-verification switches, and a retry threshold before anything is declared down. A scheduler polls them continuously (previously checks only ran when someone pressed a button), outages open and close an incident on their own, and each monitor gets a detail page with a response-time chart, a 90-day uptime strip, a live check log and TLS certificate expiry. Host CPU/memory/disk alerting is unchanged and now shares one Incidents timeline with monitor outages, so "something is wrong" is a single place. Status pages publish monitors you already have rather than defining their own duplicate probes.- **Monitoring Navigation** - Monitors, Incidents, Events and Jobs are tabs of one Monitoring group instead of scattered top-level pages, and the events stream was rebuilt on the same search-and-filter layout as the rest of the panel.- **Themes & Theme Studio** - A gallery of color themes in Settings → Appearance (Paper, Nord Deep, Gruvbox, Phosphor, High Contrast, and the stock look), applied instantly and previewed live, kept as each user's personal choice on top of the dark/light toggle. Themes are data, not code — a small map of color tokens — so a built-in Theme Studio lets anyone edit colors over the live panel and export a shareable file, admins can set a panel-wide default or import a theme, and a public community registry installs themes with one click.diff --git a/docs/DEPLOYMENT.md b/docs/DEPLOYMENT.mdindex 4b47448e..f88b2d56 100644--- a/docs/DEPLOYMENT.md+++ b/docs/DEPLOYMENT.md@@ -307,12 +307,24 @@ Docker volumes):### Auto-renew SSL Certificate+Certbot installs its own renewal timer, and host nginx reads the certificates+straight out of `/etc/letsencrypt/live/`, so there is nothing to copy and no+container to restart. Verify it is armed:+```bash-# Add to crontab-sudo crontab -e+# The renewal timer certbot installed+systemctl list-timers | grep certbot++# Dry-run a renewal without touching the live certificate+sudo certbot renew --dry-run+```-# Add this line (renews at 2:30 AM daily)-30 2 * * * certbot renew --quiet && cp /etc/letsencrypt/live/yourdomain.com/*.pem /opt/serverkit/nginx/ssl/ && docker compose -f /opt/serverkit/docker-compose.yml restart frontend+Only if the timer is missing, add a cron entry that reloads host nginx:++```bash+sudo crontab -e+# Renew at 2:30 AM daily, reload nginx only when something actually renewed+30 2 * * * certbot renew --quiet --deploy-hook "systemctl reload nginx"```### Change Domain@@ -335,15 +347,22 @@ DATABASE_URL=postgresql://user:pass@localhost:5432/serverkit## Troubleshooting-### Container won't start+### Panel won't start++This guide covers the **host install**, where the panel is a systemd service and+not a container — do not reach for `docker compose` here, it would build a second,+separate all-in-one panel beside this one.```bash# Check logsserverkit logs backend-# Rebuild-docker compose build --no-cache-docker compose up -d+# Restart the service+serverkit restart+serverkit status++# Deeper diagnosis+serverkit doctor```### Permission denied errors@@ -360,21 +379,18 @@ sudo usermod -aG docker $USER### Port already in use```bash-# Find what's using port 80+# Find what's using port 80 (host nginx) or 5000 (the panel backend)sudo lsof -i :80--# Stop the service or change PORT in .env+sudo lsof -i :5000```### Reset everything```bash-# Stop and remove all containers and volumes-serverkit stop-docker compose down -v+# Delete all managed apps, containers, folders and orphaned Docker resources+serverkit factory-reset-# Rebuild from scratch-docker compose build --no-cache+# Bring the panel back upserverkit startserverkit init-dbserverkit create-admindiff --git a/docs/INSTALLATION.md b/docs/INSTALLATION.mdindex dc5fb501..458759f4 100644--- a/docs/INSTALLATION.md+++ b/docs/INSTALLATION.md@@ -55,6 +55,9 @@ On a `minimal` install:| `SERVERKIT_PROFILE=minimal\|standard\|full` | Pick the install profile and skip the prompt || `SERVERKIT_PROFILE_TIMEOUT=15` | Seconds to wait at the profile prompt before taking the suggestion || `SERVERKIT_SKIP_SSL=1` | Skip HTTPS/certbot entirely |+| `SERVERKIT_EXTERNAL_PROXY=1` | You run your own TLS-terminating reverse proxy in front. Selects the plain-HTTP nginx site (no redirect for the proxy to loop on), skips certbot, and sets `TRUST_PROXY_HEADERS=true` + `TRUSTED_PROXY_HOPS=2`. See [Running behind your own reverse proxy](#running-behind-your-own-reverse-proxy) |+| `SERVERKIT_PUBLIC_URL=https://panel.example.com` | The public URL browsers use. Required with `SERVERKIT_EXTERNAL_PROXY` — without it websocket connections are rejected on origin |+| `SERVERKIT_CONFIG=/path/install.conf` | Read the options above from a `KEY=VALUE` file instead of the command line. Explicit environment still wins || `INSTALL_FROM_RELEASE=1` | Install from the latest GitHub release tarball instead of cloning source || `SERVERKIT_VERSION=v1.7.0` | Pin a specific release version || `SERVERKIT_OFFLINE_TARBALL=/path/to/...tar.gz` | Use a local tarball instead of downloading |@@ -79,6 +82,26 @@ curl -fsSL https://serverkit.ai/install.sh | \sudo SERVERKIT_OFFLINE_TARBALL=/tmp/serverkit-v1.7.0-linux-amd64.tar.gz bash```+Example behind your own Caddy/Traefik:++```bash+curl -fsSL https://serverkit.ai/install.sh | \+ sudo SERVERKIT_EXTERNAL_PROXY=1 SERVERKIT_PUBLIC_URL=https://panel.example.com bash+```++Example re-runnable install from a config file:++```bash+cat > /root/serverkit.conf <<'EOF'+SERVERKIT_PROFILE=standard+SERVERKIT_EXTERNAL_PROXY=1+SERVERKIT_PUBLIC_URL=https://panel.example.com+EOF++curl -fsSL https://serverkit.ai/install.sh | \+ sudo SERVERKIT_CONFIG=/root/serverkit.conf bash+```+## Updating ServerKit```bash@@ -114,6 +137,7 @@ sudo SERVERKIT_MIRROR_URL=https://mirror.example.com/releases serverkit update- [Requirements](#requirements)- [Quick Install (Docker)](#quick-install-docker)- [Manual Installation](#manual-installation)+- [Running behind your own reverse proxy](#running-behind-your-own-reverse-proxy)- [Post-Installation Setup](#post-installation-setup)- [Security Configuration](#security-configuration)- [Notification Setup](#notification-setup)@@ -146,7 +170,16 @@ For manual installation:## Quick Install (Docker)-This is the recommended installation method.+`docker compose up -d` runs ServerKit as a **single container**: gunicorn serves+the API, the React SPA and the Socket.IO websockets together on port 5000. There+is no nginx inside it.++> ⚠️ **A containerised panel cannot manage its own host.** It has no systemd, no+> host nginx and no host package manager, so managed sites, per-app vhosts and+> host services are unavailable. Use it for evaluation, for driving *other*+> servers through agents, or as a panel behind your own reverse proxy. To manage+> **this** machine, use the [one-line host install](#one-line-install-recommended)+> instead.### Step 1: Install Docker@@ -206,6 +239,12 @@ nano .env- `SECRET_KEY` - Unique random string for Flask sessions- `JWT_SECRET_KEY` - Unique random string for JWT tokens- `CORS_ORIGINS` - Your domain (e.g., `https://panel.yourdomain.com`)+- `SERVERKIT_HTTP_PORT` - Optional; host port to publish (default `5000`)++Leave the database alone unless you want PostgreSQL: compose keeps SQLite on the+`serverkit-data` volume. To use another database under Docker, set+`SERVERKIT_DATABASE_URL` — **not** `DATABASE_URL`, which compose overrides so a+relative SQLite path cannot silently place your data outside the volume.### Step 4: Start ServerKit@@ -222,12 +261,18 @@ docker compose ps### Step 5: Access ServerKit-Open your browser and navigate to:-- **HTTP**: `http://your-server-ip`-- **HTTPS**: `https://your-server-ip` (if SSL configured)+Open your browser and navigate to `http://your-server-ip:5000` (override the+published port with `SERVERKIT_HTTP_PORT` in `.env`).Create your admin account on first visit.+The container speaks plain HTTP only — it has no certificates and no HTTPS+listener. For TLS, terminate it in a reverse proxy in front of the container:+see [Running behind your own reverse proxy](#running-behind-your-own-reverse-proxy).++Your data (the SQLite database) lives on the `serverkit-data` named volume, so+`docker compose down` keeps it and `docker compose down -v` destroys it.+---## Manual Installation@@ -441,6 +486,230 @@ sudo systemctl status certbot.timer---+## Running behind your own reverse proxy++Already running Caddy, Traefik, Nginx Proxy Manager or your own nginx — with+Let's Encrypt, an internal PKI, or a private CA such as smallstep? ServerKit+supports that. The panel itself is CA-agnostic: certificates are entirely your+proxy's business, and ServerKit never sees them.++Two things make it work, and one thing usually breaks first.++### The redirect loop++A **host install** puts its own nginx on port 80, and the default site 301s+every plain-HTTP request to HTTPS. An external proxy terminates TLS and then+speaks plain HTTP upstream — so it receives that 301, follows it, gets another,+and the browser gives up with *"too many redirects"*. The fix is to stop that+redirect (topology A below) or to bypass that nginx entirely (topology B).++Nothing in the Flask app ever redirects to HTTPS, so once nginx is out of the+way the loop cannot recur.++### Pick a topology++| | **A — proxy → ServerKit nginx** | **B — proxy → the app directly** |+|---|---|---|+| Install type | Host install (`install.sh`) | Docker, or a host install you front yourself |+| Upstream | `127.0.0.1:80` | `127.0.0.1:5000` |+| Panel UI / API / websockets | ✅ | ✅ |+| Managed site vhosts, per-app domains | ✅ | ❌ **panel only** |+| `TRUSTED_PROXY_HOPS` | `2` | `1` |++Topology B is the only option for the Docker image — it contains no nginx.+Choose A on a host install if ServerKit also hosts your sites, because those+per-app vhosts live in the nginx you would be bypassing.++### The two environment variables++Both go in `.env` (host install: `/opt/serverkit/.env`) and both matter+regardless of topology.++| Variable | Why |+|---|---|+| `SERVERKIT_PUBLIC_URL` | **Required.** The browser's `Origin` on the Socket.IO handshake is your public HTTPS URL, which the panel does not otherwise know. Without it every realtime connection is rejected with HTTP 400 and the UI silently stops updating. Set it to the exact scheme+host you browse to, no trailing slash. |+| `TRUST_PROXY_HEADERS` | Set `true` so the real client IP is read from `X-Forwarded-For` instead of every request appearing to come from your proxy. Rate limits, login lockout and audit logs all depend on it. ⚠️ Leave it **off** if the port is exposed directly to clients — the header is client-forgeable without a proxy in front to overwrite it. |++```bash+SERVERKIT_PUBLIC_URL=https://serverkit.example.com+TRUST_PROXY_HEADERS=true+TRUSTED_PROXY_HOPS=1 # 2 for topology A — see the table above+```++`TRUSTED_PROXY_HOPS` is the number of proxies that append to `X-Forwarded-For`+before Flask sees it. Count them: in topology A your proxy appends the client,+then ServerKit's nginx appends your proxy, so it is `2`. Too low and you log+your own proxy's IP; too high and a client can forge the value.++### Topology A — keep ServerKit's nginx, drop the redirect++The plain-HTTP site ships with every install; it just isn't the default.++```bash+# 1. Serve the panel over plain HTTP, with no redirect for your proxy to loop on+sudo ln -sf /etc/nginx/sites-available/serverkit-insecure.conf \+ /etc/nginx/sites-enabled/serverkit.conf++# 2. Record that this box does not terminate TLS itself+echo insecure | sudo tee /etc/serverkit/ssl-mode+sudo sed -i 's/^SERVERKIT_SSL_MODE=.*/SERVERKIT_SSL_MODE=insecure/' /opt/serverkit/.env++# 3. Add the two variables from above to /opt/serverkit/.env, then apply+sudo nginx -t && sudo systemctl reload nginx+sudo systemctl restart serverkit+```++> Run these **on the host**, not inside a container — `serverkit-insecure.conf`+> is written to the host filesystem by `install.sh` and does not exist in any+> ServerKit image.++Step 2 is not cosmetic: it is what suppresses the panel's+`Strict-Transport-Security` header. Left as `secure`, the panel tells browsers+to force HTTPS on a port that only speaks HTTP. **Both** places must change —+the panel reads the `SERVERKIT_SSL_MODE` environment variable first and only+falls back to `/etc/serverkit/ssl-mode`, so editing the file alone has no effect+on a host install, where `install.sh` wrote that variable into `.env`.++To start a **new** install already in this shape, skip the manual steps:++```bash+curl -fsSL https://serverkit.ai/install.sh -o install.sh+sudo SERVERKIT_EXTERNAL_PROXY=1 \+ SERVERKIT_PUBLIC_URL=https://serverkit.example.com \+ bash install.sh+```++`SERVERKIT_EXTERNAL_PROXY=1` selects the plain-HTTP site, skips certbot, and+writes `TRUST_PROXY_HEADERS=true` + `TRUSTED_PROXY_HOPS=2` into `.env` for you.+See [Install options](#install-options).++### Topology B — point your proxy at the app++Docker needs nothing but the environment — the shipped `docker-compose.yml`+already publishes the panel on 5000:++```bash+# .env+SERVERKIT_PUBLIC_URL=https://serverkit.example.com+TRUST_PROXY_HEADERS=true+TRUSTED_PROXY_HOPS=1+```++```bash+docker compose up -d+```++The container publishes on all interfaces by default, so port 5000 is reachable+directly and bypasses your proxy (and its TLS). If the proxy runs on the same+host, bind the panel to loopback with a `docker-compose.override.yml`:++```yaml+services:+ serverkit:+ ports: !override+ - "127.0.0.1:5000:5000"+```++Otherwise, block 5000 at the firewall.++On a host install, point your proxy at `127.0.0.1:5000` and leave ServerKit's+nginx alone (or disable it if it fights for port 80). Gunicorn serves the SPA,+the API and the websockets from that single port. Remember this is panel-only:+managed sites do not exist without the vhost layer.++### Proxy configuration++Substitute `UPSTREAM` with `localhost:80` (topology A) or `localhost:5000`+(topology B). Websockets need no special handling in Caddy or Traefik; nginx and+Apache need the upgrade headers spelled out.++**Caddy** — including a private ACME CA such as smallstep:++```caddy+{+ # Only if you use an internal CA. Omit both lines for Let's Encrypt.+ acme_ca https://ca.lab/acme/acme/directory+ acme_ca_root /etc/caddy/root_ca.crt+}++serverkit.example.com {+ reverse_proxy UPSTREAM+}+```++**Traefik** (dynamic file provider):++```yaml+http:+ routers:+ serverkit:+ rule: "Host(`serverkit.example.com`)"+ service: serverkit+ tls:+ certResolver: internal+ services:+ serverkit:+ loadBalancer:+ servers:+ - url: "http://UPSTREAM"+```++**Nginx Proxy Manager**: add a Proxy Host for the domain, forward to the+upstream host/port over `http`, and enable **Websockets Support** — the panel's+realtime updates fail silently without it.++**Plain nginx** elsewhere on your network:++```nginx+server {+ listen 443 ssl;+ server_name serverkit.example.com;++ ssl_certificate /etc/ssl/certs/serverkit.crt;+ ssl_certificate_key /etc/ssl/private/serverkit.key;++ location / {+ proxy_pass http://UPSTREAM;+ proxy_http_version 1.1;+ proxy_set_header Upgrade $http_upgrade;+ proxy_set_header Connection "upgrade";+ proxy_set_header Host $host;+ proxy_set_header X-Real-IP $remote_addr;+ proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;+ proxy_set_header X-Forwarded-Proto $scheme;+ proxy_read_timeout 7d; # long-lived websockets+ proxy_send_timeout 7d;+ }+}+```++### Private and internal CAs++ServerKit needs no configuration for these — your proxy presents the+certificate, and only browsers and other clients have to trust the issuing root.+Install your root CA in the OS/browser trust store on the machines you browse+from.++One exception: if a **ServerKit agent** on another machine dials back to a panel+fronted by a private CA, that machine must also trust the root, or the agent's+TLS handshake fails. Install the root in its system trust store+(`/usr/local/share/ca-certificates/` + `update-ca-certificates` on Debian/Ubuntu,+`/etc/pki/ca-trust/source/anchors/` + `update-ca-trust` on RHEL-family).++### Troubleshooting++| Symptom | Cause |+|---|---|+| *"Too many redirects"* | Topology A step skipped — ServerKit's nginx is still 301ing to HTTPS. Check `readlink /etc/nginx/sites-enabled/serverkit.conf`. |+| Loop persists after the fix | Your browser cached an HSTS entry from an earlier HTTPS visit. Clear it (`chrome://net-internals/#hsts` → *Delete domain security policies*) and confirm `/etc/serverkit/ssl-mode` reads `insecure`. |+| UI loads, but nothing live-updates; console shows a failed `/socket.io/` request | `SERVERKIT_PUBLIC_URL` unset or not an exact match for the URL in the address bar (scheme, host, no trailing slash). Restart the panel after changing it. |+| Websockets fail only through the proxy | Upgrade headers or Websockets Support not enabled on the proxy. |+| Every audit-log entry and rate limit shows your proxy's IP | `TRUST_PROXY_HEADERS` is not `true`. |+| Client IPs are wrong but not the proxy's | `TRUSTED_PROXY_HOPS` mismatch — recount the proxies in front of Flask. |+| 502 from your proxy | Nothing is listening on the upstream. Check `serverkit status` / `docker compose ps`, and that the upstream port matches the topology. |++---+## Post-Installation Setup### 1. Create Admin Accountdiff --git a/docs/LOCAL_DEVELOPMENT.md b/docs/LOCAL_DEVELOPMENT.mdindex b2862600..81893c74 100644--- a/docs/LOCAL_DEVELOPMENT.md+++ b/docs/LOCAL_DEVELOPMENT.md@@ -115,65 +115,28 @@ Frontend will be available at: `http://localhost:41921`Use this for quick UI testing. Note: System management features (PHP install, firewall, etc.) won't work.-### docker-compose.dev.yml--Create this file in the project root:--```yaml-# Development docker-compose - FOR TESTING UI ONLY-# System management features won't work in this mode--services:- backend:- build:- context: ./backend- dockerfile: Dockerfile- container_name: serverkit-backend-dev- environment:- - FLASK_ENV=development- - SECRET_KEY=dev-secret-key- - JWT_SECRET_KEY=dev-jwt-key- - DATABASE_URL=sqlite:////app/instance/serverkit.db- - CORS_ORIGINS=http://localhost,http://localhost:3000,http://localhost:5849- ports:- - "5849:5000"- volumes:- - ./backend:/app- - dev-data:/app/instance- networks:- - serverkit-dev-- frontend:- build:- context: ./frontend- dockerfile: Dockerfile.dev- container_name: serverkit-frontend-dev- environment:- - VITE_API_URL=http://localhost:5849/api/v1- ports:- - "3000:3000"- volumes:- - ./frontend:/app- - /app/node_modules- depends_on:- - backend- networks:- - serverkit-dev--networks:- serverkit-dev:- driver: bridge--volumes:- dev-data:+The repository's `docker-compose.yml` already does this — it builds the+all-in-one image from `Dockerfile` (gunicorn serving the API, the SPA and+websockets together) and publishes it on port 5000.++```bash+cp .env.example .env # set SECRET_KEY / JWT_SECRET_KEY+docker compose up -d --build```-### Run with Docker Compose+Then open http://localhost:5000. Override the published port with+`SERVERKIT_HTTP_PORT` in `.env` if 5000 is taken.```bash-docker compose -f docker-compose.dev.yml up --build+docker compose logs -f # follow the panel log+docker compose down # stop, keep the database volume+docker compose down -v # stop and destroy the database```+There is no hot reload in this mode — the SPA is a production build baked into+the image, so a frontend change needs `docker compose up -d --build`. For an+edit-refresh loop, use Option 1 (Vite HMR + Flask reloader).+---## Option 3: VS Code Dev Container@@ -183,8 +146,8 @@ Add this to `.devcontainer/devcontainer.json`:```json{"name": "ServerKit Dev",- "dockerComposeFile": "../docker-compose.dev.yml",- "service": "backend",+ "dockerComposeFile": "../docker-compose.yml",+ "service": "serverkit","workspaceFolder": "/app","customizations": {"vscode": {@@ -195,8 +158,8 @@ Add this to `.devcontainer/devcontainer.json`:]}},- "forwardPorts": [5000, 3000],- "postCreateCommand": "pip install -r requirements.txt"+ "forwardPorts": [5000],+ "postCreateCommand": "pip install -r backend/requirements.txt"}```diff --git a/docs/README.es.md b/docs/README.es.mdindex 13b75f26..3b640ef2 100644--- a/docs/README.es.md+++ b/docs/README.es.md@@ -86,9 +86,16 @@ base de datos, migración y rollback automático. Usa `--dry-run` para previsualgit clone https://github.com/jhd3197/ServerKit.gitcd ServerKitcp .env.example .env # luego edita .env con tus claves-docker compose up -d # accede en http://localhost+docker compose up -d # accede en http://localhost:5000```+Ejecuta el panel como un único contenedor. Ten en cuenta que un panel en+contenedor **no puede administrar su propio host** — sin systemd, sin nginx del+host, sin vhosts de sitios gestionados; para eso usa la Opción 1. No incluye+nginx y nunca redirige a HTTPS, así que es el destino ideal para poner tu propio+proxy inverso delante — consulta+[Ejecutar detrás de tu propio proxy inverso](INSTALLATION.md#running-behind-your-own-reverse-proxy).+### Opción 3: Instalación ManualConsulta la [Guía de Instalación](INSTALLATION.md) para instrucciones paso a paso.diff --git a/docs/README.pt.md b/docs/README.pt.mdindex d70c07cd..a122225e 100644--- a/docs/README.pt.md+++ b/docs/README.pt.md@@ -86,9 +86,16 @@ ou `--release [versão]` para tarballs de release.git clone https://github.com/jhd3197/ServerKit.gitcd ServerKitcp .env.example .env # depois edite o .env com suas chaves secretas-docker compose up -d # acesse em http://localhost+docker compose up -d # acesse em http://localhost:5000```+Executa o painel como um único contêiner. Note que um painel em contêiner **não+consegue gerenciar o próprio host** — sem systemd, sem nginx do host, sem vhosts+de sites gerenciados; para isso use a Opção 1. Ele não inclui nginx e nunca+redireciona para HTTPS, o que o torna o alvo ideal para colocar seu próprio proxy+reverso na frente — consulte+[Rodar atrás do seu próprio proxy reverso](INSTALLATION.md#running-behind-your-own-reverse-proxy).+### Opção 3: Instalação ManualConsulte o [Guia de Instalação](INSTALLATION.md) para instruções passo a passo.diff --git a/docs/README.zh-CN.md b/docs/README.zh-CN.mdindex 89cf55aa..bb67d683 100644--- a/docs/README.zh-CN.md+++ b/docs/README.zh-CN.md@@ -86,9 +86,14 @@ sudo serverkit updategit clone https://github.com/jhd3197/ServerKit.gitcd ServerKitcp .env.example .env # 编辑 .env 文件,填入你的密钥-docker compose up -d # 访问 http://localhost+docker compose up -d # 访问 http://localhost:5000```+以单容器方式运行面板。请注意,容器化的面板**无法管理它自己的宿主机**——没有 systemd、+没有宿主机 nginx、没有托管站点的 vhost;需要这些功能请使用方式一。该镜像不含 nginx,+也从不重定向到 HTTPS,因此非常适合放在你自己的反向代理后面——参阅+[在你自己的反向代理后运行](INSTALLATION.md#running-behind-your-own-reverse-proxy)。+### 方式三:手动安装参阅 [安装指南](INSTALLATION.md) 获取详细的分步说明。