Skip to content

v1.32.0 is out small homelab tools in search and cleaner feed titles

nextDash

Features

Install

One container, one folder, one port.

nextDash runs as one container with one folder and one port. There is no database to set up, no migration to run and no account to create.

Running Unraid? Jump to the Unraid install →

Bring it up and open it. A new install opens on its dashboard with example links, and after a moment a Quick start guide grows out of a bar at the bottom: keep the example links to look around or start with an empty page, pick the language and the weather, give your name for the greeting in the About you box, then work through ten next steps at your own pace. Close it and it folds back into the bar until you need it. Bring your bookmarks along by importing an HTML export from Chrome, Firefox or Edge, or an export from Pocket, Pinboard, Raindrop, linkding, Shiori, Linkwarden or Karakeep. Folders become categories, and tags, notes and the saved date come along.

Install

Pick the way that fits your server. Docker Compose is the usual one, Unraid has its own template, and a single Go binary runs anywhere Go builds.

Docker Compose

Save this as docker-compose.yml:

services:
  nextDash:
    image: ghcr.io/jordibrouwer/nextdash:latest
    container_name: nextDash
    ports:
      - "8080:8080"
    volumes:
      - ./data:/app/data
    environment:
      - PORT=8080
    restart: unless-stopped

Start it with docker compose up -d and open http://localhost:8080. The image is multi-arch, so it runs on x86 servers and on a Raspberry Pi alike.

  • One folder holds everything. Bookmarks, settings, icons and backups all live in ./data. Back that folder up and you have backed up nextDash.
  • Another port. Change the left side of "8080:8080", for example "8099:8080". Inside the container the port stays 8080.
  • Update. docker compose pull && docker compose up -d. Your data stays where it is.
  • From a git checkout. docker-compose.prod.yml is the production file and mounts only ./data. docker-compose.yml is for development. Put your own mounts and variables in a docker-compose.override.yml next to it, and your changes stay out of the checkout.
  • Never delete ./data while the container runs. The container keeps writing into a folder that no longer exists, and the data is gone at the next restart. Stop it first: docker compose down, then delete, then docker compose up -d.

To let the Containers view and the server widgets see the machine, mount the Docker socket and the host folders read only. The write token and the Docker actions are off until you set them. The security chapter explains both.

Go

nextDash is one Go binary with its pages, scripts and languages built in. You need Go 1.26 or newer.

git clone https://github.com/jordibrouwer/nextDash.git
cd nextDash
go build -o nextDash
./nextDash

It listens on port 8080 and keeps its data in ./data next to the binary. Set PORT to listen elsewhere and NEXTDASH_DATA_DIR to keep the data in another folder, for example PORT=8099 NEXTDASH_DATA_DIR=/srv/nextdash ./nextDash.

The main branch is the released code, and the one to clone for self-hosting. dev is for contributing. To keep the binary running, put it under systemd or any process manager you already use, and put a reverse proxy in front for HTTPS.

Unraid

nextDash is in Unraid’s Community Applications, so there is no compose file to write.

  1. Open the Apps tab and search for nextDash.
  2. Click Install. The template opens with every row filled in.
  3. Check the rows below, then click Apply. Unraid pulls the image and starts the container.
  4. Open it from the Docker tab: click the icon and choose WebUI, or go to http://<server>:8103.
Row Default What it is
WebUI Port 8103 The port on the server. Change it if something else uses it.
AppData /mnt/user/appdata/nextdash/ All your data. Back it up with the rest of appdata.
Write token empty A long random string. Needed before the Containers view may start or stop anything.
Trusted proxies empty The address of your reverse proxy, when nextDash sits behind one.
Host proc, Host disks /proc, /mnt, read only Let the Processor, Memory and Disks widgets read the server instead of the container.
Docker socket /var/run/docker.sock, read only Lets the Containers widget and view see the server’s containers.
Docker actions 0 Set to 1 to start, stop, restart and update containers from nextDash. Needs the write token.
Run as root 0 Leave at 0. Unraid’s socket belongs to the docker group, which nextDash joins on its own.

Only the port and AppData matter at first. Without the rest, nextDash is a plain bookmark dashboard, and you can add the rows later under Docker, nextDash, Edit.

After the first launch

  • Disks. In the Disks widget, name /mnt/user for the whole array and /mnt/cache for the cache pool. /mnt/diskN shows one disk.
  • Unraid widgets. Seven widgets read the server through Unraid’s own API: overview, array, parity, shares, VMs, UPS and notifications. They need an API key with the role Viewer, set once under Config, Unraid.
  • A look that fits. Unraid Black, Unraid Azure, Unraid Ember and Unraid Blaze follow Unraid’s own colours, each in dark and light.
  • Updates. Unraid shows update ready on the Docker tab when a new image is out. Click it, or let the Auto Update Applications plugin do it.

Try it

  1. Bring it up with one of the installs above and open it.
  2. Press > to search, : for commands and Shift + 1 for the cheat sheet. Everything else can wait.

There are no user accounts, so keep nextDash on a trusted network. The trust page covers three safe ways to run it.

The nextDash dashboard with the Quick start bar at the bottom
The dashboard, with the Quick start bar at the bottom.
The Quick start guide: keep the example links or start empty, the language, the weather and the next steps
The Quick start guide, open over a new install.

Bringing your bookmarks

An import asks where the bookmarks go: onto the dashboard, or into the Inbox first, so you can sort them before they land on a page.

The first launch, step by step

  1. 1Open the address: the dashboard comes first, with example links
  2. 2Wait a moment: the Quick start bar slides in at the bottom
  3. 3Choose Keep these example links, or Start with an empty page
  4. 4Pick a language and the weather in the guide
  5. 5Work through the next steps at your own pace
  6. 6Close the guide: it folds back into the bar
  • 98example links on two pages
  • 10next steps in the guide
  • 3ways to install
  • 1folder for all your data

Three seconds after the bar is up, the guide grows out of it once, so you meet it first. Closing it folds it back into the bar, and after that it only opens when you press the bar. Start with an empty page asks first, and then removes the example links and their categories from the first page. Its widgets stay.

What the guide holds

On the left are the choice about the example links, the weather and the manual. On the right are a CSV import and three ready-made pages: Homelab, Media server and Developer. A CSV file needs a url column, and name, category, tags and notes are optional. For a ready-made page you type your server’s address once, and it fills in every service.

There are ten next steps: take the one-minute tour, open the Bookmarks view, browse by tag, open the Inbox view, add a widget, turn on status checks, set up notifications, open the Config settings, learn the shortcuts and add a second page. Three show at a time, and each one ticks itself off when you do it. On an Unraid server there is an eleventh, Connect your Unraid server.

Step 1 of 10 of the dashboard tour: a drawing of the action bar keys for add, search, commands, finders, tag cloud, recent, pages, fold all and cheat sheet
The one-minute tour shows the keys of the action bar.

The example bookmarks

If you keep the example links, a new install starts with 98 of them on two pages, so there is something to try search, tags and the keys on. The main page has Development, Docker, Unraid, Self-hosted, Tools and Daily, the Today collection and three widgets. The news page has Tech news, Dev & blogs, Security, Communities, Videos and News. The Inbox starts with ten example links that are not on any page. With the Docker socket mounted, a card offers the apps running on the server as bookmarks.

The first hour

Split your bookmarks across a few pages, give the ten you open daily a shortcut, and switch on link checking under Config, Monitoring, Checks. Everything else can wait until you know what you want.

If the data folder goes missing

With a bind mount, deleting ./data while the container runs leaves it writing into a folder that no longer exists, and nothing in the app shows it. If docker ps shows the container running while ./data is gone from the host, copy the data back out first, then recreate the container so the mount points at the new folder. nextDash is the container_name from the compose file above.

docker exec nextDash tar cf - -C /app data | tar xf - -C .
docker compose up -d --force-recreate