Guide · Open source
How to use linux-dash: install and run it on Linux
Updated · written with AI from the project's own documentation and checked against our catalogue data
linux-dash is an open-source web dashboard that shows system information for a Linux machine in your browser. This guide walks through cloning the repository, starting the recommended Node.js server, and changing its port and host. It also covers the security caveat in the README, which matters before you run it anywhere other than a private network.
Quick start
- 1Clone the repository. Run git clone --depth 1 on the linux-dash repository, then change into linux-dash/app/server.
- 2Install dependencies. Run npm install --production inside the server directory to install what the Node.js server needs.
- 3Start the server. Run node index.js. The server listens on port 80 by default and may need sudo.
- 4Set port and host. Use LINUX_DASH_SERVER_PORT and LINUX_DASH_SERVER_HOST, or the --port and --host flags, to change where it listens.
- 5Open the dashboard. Open the address of your machine in a browser using the port you chose to view the system information.
- 6Protect the install. Add your own security measure, since linux-dash has no built-in security or authentication.
What linux-dash does and who it suits
linux-dash is described in its README as a simple, low-overhead web dashboard for Linux systems. It is meant to be easy to drop in and run, so you can view a machine's health in a browser without a large setup.
It fits people who want a quick browser view of a Linux server, developers running a small personal or lab machine, and anyone who wants a lightweight monitor. It is not a fit for production servers exposed to the internet, and the README does not mention alerting, history, or multi-server monitoring.
- Small: under 400KB on disk with .git removed, per the README
- Ships with server versions in Node.js, Go, Python, and PHP
- Licence: MIT
Get the code: clone or download the repository
The README recommends cloning the repository with a shallow depth of one, then moving into the server directory. If you prefer not to use git, it also offers a zip download.
- Clone the repo, then go to the server directory (Node.js path)
- Or download the zip, unzip it, and go to linux-dash-master/app/server
git clone --depth 1 https://github.com/afaqurk/linux-dash.git
cd linux-dash/app/serverInstall dependencies and start the Node.js server
Node.js is the recommended server option. The README does not state a required Node.js version, so check your installed version before you begin. Install dependencies with npm, then start the server with node index.js.
By default the server listens on port 80, and the README notes that this may require sudo. It also listens on every network interface (0.0.0.0) unless you change that.
npm install --production
node index.jsChange the port and host
You can set the port with the LINUX_DASH_SERVER_PORT environment variable or a --port flag. You can set the listening address with LINUX_DASH_SERVER_HOST or a --host flag. Binding to 127.0.0.1 keeps the dashboard reachable only from the machine itself.
- Port: LINUX_DASH_SERVER_PORT, for example 8080
- Host: LINUX_DASH_SERVER_HOST, for example 127.0.0.1
LINUX_DASH_SERVER_PORT=8080 node server
LINUX_DASH_SERVER_HOST=127.0.0.1 node serverOther server options: Go, Python and PHP
The README covers the same dashboard on other stacks. For Go, you can run it directly or build a binary. For Python, you start index.py. For PHP, you must enable the exec, shell_exec, and escapeshellarg functions, point your web server at the app/ directory, and restart it. The README links external tutorials for Apache and nginx setup.
- Go: go run index.go, or go build and then ./server -h for binary options
- Python: python index.py
- PHP: enable exec, shell_exec, escapeshellarg; point the web server at app/
go run index.go
python index.pySecure it before you expose it
The README says it is strongly recommended to protect every installation with a security measure of your choice. linux-dash does not provide any security or authentication features. Keep it on a trusted network, bind it to localhost, or place it behind your own access control. Do not expose it directly to the internet.
- Do not run it on production servers exposed to the internet
- Use your own protection, such as a firewall or access control, as the README advises
What people use it for
- Glancing at the health of a small personal Linux server from a browser
- Monitoring a lab or development machine without a heavy setup
- Dropping a lightweight dashboard onto a Linux box on a private network
Frequently asked questions
Is linux-dash free?
linux-dash is released under the MIT licence, according to the repository. The README does not list any paid tier.
What do I need to run linux-dash?
The README names Node.js as the prerequisite for the recommended server option but does not state a version. Go, Python, or PHP are alternative server options described in the README.
Does linux-dash have a login or password?
No. The README says linux-dash does not provide any security or authentication features, so you need to protect it yourself.
Why does linux-dash run on port 80?
Port 80 is the default in the README for every server option. You can change it with the LINUX_DASH_SERVER_PORT environment variable or the --port flag.
Can I run linux-dash on the internet?
The README does not recommend this. It is intended for simple, low-overhead local use, and any public exposure needs your own security measure.
How does linux-dash compare to Glances, Netdata, or Cockpit?
Glances, Netdata, and Cockpit are comparable projects in the same space. The README does not compare linux-dash with them, so check each project's documentation for features like history, alerting, or multi-server monitoring.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
linux-dash suits people who want a quick, lightweight browser view of one Linux machine on a private network, such as a lab or personal server. If you need authentication out of the box, alerting, history, or monitoring across many servers, the README does not cover those, so consider an alternative such as Glances, Netdata, or Cockpit.
Install options & downloads