
Show HN: Just Dashboard, an open-source VPS management dashboard
Your whole Linux server, in one private control panel.
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
Your whole Linux server, in one private control panel.
Deploy apps, run Docker, manage databases, shape the network, open a real shell and keep it all backed up — behind one login that lives on your private network.
Version 0.7.4 · Go backend · Next.js frontend · one docker compose stack
just-dashboard.com · Install · Features · Tour · Admin scripts · Security · Configuration · Support
Screenshots show version 0.7.1 with example data.
It says why: a server that is waiting rather than busy, a container killed for its memory limit. Where it can fix a finding, the finding comes with a button.
Root-equivalent power belongs behind Tailscale or an SSH tunnel. The allowlist runs before the login, two-factor is per account, and every change is audited.
No fleet, no cloud account, no AI model or API key. One docker compose stack that knows the machine it runs on, end to end.
Self-hosted and AGPL-3.0. Nothing is held back for a paid tier — every feature is free and stays free.
🖥️ Overview & monitoring
A live overview of the machine: CPU, memory, load, network, storage and disk I/O
Metrics with seven days of history the backend records itself, and CSV export
Notable moments, top processes and the day's activity at a glance
Processes, PM2 apps, systemd services and scheduled jobs, each with its verbs
One log viewer for files, containers, stacks, PM2 and the journal, with insights
Every service shows its own logs on its own page
🚀 Deployments
Deploy from a repository, an image, a Compose stack or 57 reviewed templates
Detects Node, Bun, Deno, Python, PHP, Go, Rust, Java, .NET, Ruby, Elixir and more
Push to deploy, plus pull-request previews only your tailnet can reach
Immutable releases, one-click rollback and health-gated cutover
Build logs, runtime, console, request logs and traffic alerts per project
Request insights that count real visitors apart from bots, with their devices and pages
Notifications to Discord, Slack, Telegram, e-mail, webhooks and GitHub
🐳 Docker
Overview of what every container uses and what just happened to it
Containers, stacks, images, volumes, networks and events, each a page
Create from a template, a pasted docker run or a form
Crash loops, failing health checks and memory kills said in words
Prepared fixes for exposure, limits and security posture
Browse a volume's or a container's files in place
🗄️ Databases
A control center for every database on the server — even unconnected ones
PostgreSQL, MySQL, MariaDB, SQLite, SQL Server, ClickHouse, Oracle, MongoDB, Redis
Table editor with staged, reviewed edits and a SQL editor with plans
Schema browser, diagram, code generation, performance and an advisor
Key browser and console for Redis, documents and pipelines for MongoDB
Protected connections, dump backups, accounts, grants and a live map
🧰 Workspace
A real terminal whose sessions survive the tab closing and dashboard restarts
Split panes, drag-and-drop docking and one-click Codex and Claude launchers
A file manager with search, previews, Monaco and image editors
A full Git workspace: staging by line, history, branches, conflicts, PR reviews
GitHub, GitLab and Gitea pull requests and Actions logs
Excalidraw: drawings with live cards for the host, projects and databases, each listed as a thumbnail of itself
Stickyboard: endless boards of sticky notes you colour, group into sections and link together
🌐 Network
A live topology of devices, tunnels and Docker networks
Interfaces, bridges, VLANs, namespaces, routing and policy rules
Firewall, port forwarding, NAT, rate limits and blocklists
WireGuard and Tailscale, DNS and ad-blocking, egress groups with failover
Traffic per device, program and container, plus speed limits and SQM
26 diagnostics, packet captures, connection paths, drift and saved runs
🔒 Proxy & TLS
Every domain drawn through nginx or Caddy to the application it reaches
Sites written as ordinary config, with a builder for auth and access rules
Certificates through certbot, including DNS wildcards, with runway at a glance
A live TLS report, streams, ports and per-site traffic
Alerts on renewals and certificate drift
🛡️ Security & backups
A verdict on the host: exposure, SSH, logins and who is attacking
fail2ban, CrowdSec and Suricata where they run
Scheduled backups to disk, S3 or Backblaze B2, and native database dumps
A coverage map of everything that is not backed up yet
Single-file and in-place restore
⚙️ Server & accounts
Host package updates on apt, dnf, yum, zypper, pacman or apk
System users, an audit log of every change and the panel's own settings
Address, certificate, allowlist and ports applied with automatic rollback
Roles, two-factor, sessions and API keys for every account
A first-run question that keeps the sections you don't use out of your sidebar
One-click self-update, with the release notes compiled in
⌨️ Everywhere
Ctrl/⌘K searches projects, sites, containers, databases, repos and pages
Previews each result with what it is connected to
Keyboard shortcuts on every page — press ? to see them
Every page remembers where you left it
A consistent, dark design built around readings rather than tiles
A quick tour
Deployments — every project, its traffic and its runs
A project — live preview, release, runtime and domains
Docker — who uses what, and what just happened
Databases — every engine on the server, each as itself
Terminal — persistent sessions and split panes
Git — stage, review and ship from the browser
Network — the server as a router, drawn live
Proxy & TLS — domains, applications and certificates
Files — browse, preview and edit anywhere you allow
Backups — what is covered, and what is not
Metrics — a week of history, recorded by the server
git clone https://github.com/JustDashboard/Just-Dashboard.git cd Just-Dashboard && sudo ./install.sh
The installer asks one question that matters — how you will reach the dashboard — then does the rest in four labelled stages:
Use ./install.sh --help to preview the steps, or sudo NO_COLOR=1 ./install.sh for plain output. Everything it asked is editable afterwards under Settings → Configuration.
First sign-in: every new account is asked once what it will use the server for — shipping apps, running databases, containers, the network, security, or working on the box — and its sidebar, Overview and search's empty list keep only those sections. Hiding a section is about the sidebar, not access: links from other pages still open it, search still finds it, and the role decides what the account may do. Account → Workspace changes the answer or asks the question again. Accounts that existed before 0.7.3 are not asked and keep every section.
Upgrading: use Update now in the dashboard, run sudo ./install.sh again, or git pull followed by docker compose up -d --build. All three keep your .env, database, accounts and sessions.
Run these on the server from your checkout. They manage dashboard accounts (not Linux users) and use the built backend image, so neither Go nor a browser login is needed — account commands work even while the backend is stopped.
Passwords are entered twice with hidden input and must meet the dashboard's strength rules. The password a script sets is the one the account signs in with — the dashboard does not ask for another at sign-in. An account an admin creates from Account → Users, and a bootstrap password the backend generated, are the ones replaced on first sign-in, after any required two-factor step. A reset clears failed-login lockout and revokes that account's sessions and API tokens, while keeping two-factor enrolment, recovery codes, role and disabled state. Account changes are audited as local root; revoke-sessions leaves API tokens unchanged.
For automation, append --password-stdin to either password command and pipe one password line from a trusted source — never put passwords in arguments or shell history. The scripts find the checkout from their own path and let Compose read .env without executing it. Run restart from SSH, since it disconnects the web terminal; it recreates containers with current settings, which docker compose restart alone does not.
This dashboard is root-equivalent. Anyone who reaches it with a valid session has root on the machine, so it is built to sit behind a VPN or an SSH tunnel — and that is enforced:
readonly limited admin
View everything ✅ ✅ ✅
Start / stop / restart, Git, edit files
✅ ✅
Terminal, delete, prune, restore, updates, accounts, firewall
✅
readonly can read any file inside JD_FILE_ROOTS, so give it to someone you would let read the disk.
This is 0.7.4. It is not 1.0 because the API is still moving. Every release is in CHANGELOG.md and in the dashboard itself, where Update now pulls, rebuilds and restarts from a container that outlives the restart. The update check is one unauthenticated GET of one file from GitHub; JD_UPDATE_CHECK=false turns it off.
Every environment variable the backend reads
The installer writes the ones that matter. These are for tuning afterwards.
Durations take a unit (12h, 60m, and the metrics settings also accept 7d); booleans take true or false. A value that cannot be parsed stops the dashboard at startup rather than falling back to the default, so a typo is visible instead of silently in effect.
cd backend && go run ./cmd/server # API on :8080 cd frontend && bun install && bun dev # UI on :3000
Set NEXT_PUBLIC_WS_BASE=http://localhost:8080 for WebSockets and JD_ALLOWED_ORIGINS=http://localhost:3000 on the backend.
Without the installer: cp .env.example .env, set JD_MASTER_KEY (openssl rand -hex 32), JD_SITE and JD_TLS, then docker compose up -d --build. The generated admin password is printed once in docker compose logs backend.
See CONTRIBUTING.md before opening a pull request.
Settings → Configuration → Danger zone → Uninstall takes the dashboard off the server and asks one question first:
Either way, databases the dashboard created, proxy sites, firewall rules, WireGuard and other network settings are left as they are, and so is the checkout. The page follows the uninstall until the dashboard stops; the whole transcript is in /var/log/just-dashboard-uninstall.log.
The dashboard's own state is a SQLite database in JD_DATA_DIR (/var/lib/just-dashboard). Back up that directory and keep JD_MASTER_KEY somewhere separate; either alone will not restore. The Backups page lists the dashboard itself under Coverage and writes that job for you.
Just Dashboard is built by one person, Wayy01, under the JustDashboard organisation. Find out more at just-dashboard.com.
The dashboard is free and every feature stays free. If it has saved you an evening, there is a Buy Me a Coffee page — entirely optional.
Sponsors. Companies and individuals who would like to sponsor the project can write to ionmoisei755@gmail.com and will be listed here with a logo and a link. No sponsors yet — the space is open.
AGPL-3.0. Run it, change it, distribute it, but if you run a modified version as a network service, publish your changes. Contributions are welcome under the terms in CONTRIBUTING.md. The product logos bundled in frontend/public/logos/ are their owners' trademarks and keep their own licences, listed in that directory's NOTICE.
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。