nextDash
🇨🇳 本应用支持简体中文。 nextDash 的界面提供中文语言选项 — 在设置中将语言切换为「中文」即可。
A keyboard-first, self-hosted bookmark dashboard. No accounts, no cloud, no noise.
My bookmark bar had become a graveyard, so I built a self-hosted dashboard that tells me which links are already dead.
Run it on any machine or container, open it in your browser, organise bookmarks across pages, and reach everything from the keyboard. Beside your bookmarks, widgets show what is going on: uptime of the services you watch, what waits in the inbox, which certificate runs out, the weather, your calendar, your feeds, your machines — and any self-hosted service that answers with JSON.
🎨 384 themes and a theme studio. 192 theme families, each with a light and a dark half, drawn from twelve materials — lacquer, glass, frost, aurora, neon, velvet, enamel, brushed metal, carbon, paper, terminal and ink — and from three collections: eight neutrals, the Looks and ThinkDashboard Classic. Aurora Glass is the default, and every material draws its own surface, category header and widget header, as a signature or in the flat Classic way. Shift + A opens the theme studio beside your dashboard and changes the real page as you go: the theme, 75 backdrops with a quiet centre behind the bookmarks, depth, glow and card glass, the category headers, the type and the contrast — or one of twelve ready-made looks that set them all at once. Compare shows what you had, 🎲 tries something at random, and nothing is saved until Apply. Search by name or material, keep up to 24 favourites, follow your system's light and dark mode, or recolour any theme and build your own in the theme editor. Manual: The new look · Manual: Appearance
Based on ThinkDashboard by MatiasDesuu.
📖 User manual (MANUAL.md) — how everything works, from the first launch to self-hosting. · Glossary
📋 Changelog (CHANGELOG.md) — every release, new and fix.
🗂️ Cheat sheet — every keyboard shortcut, printable (HTML). Press ! or F1 on the dashboard for the live list. Regenerate with npm run generate:cheatsheet.
🌐 Website: nextdash.cc
🌐 Dev log: www.jordibrw.nl
🌐 Demo: demo.nextdash.cc
🧩 Save a link from anywhere: a browser extension, a share sheet, a bookmarklet, a shell one-liner, Raycast, Dropzone 5, Alfred, Apple Shortcuts and Ulauncher — see What nextDash talks to.
🏠 Run your self-hosted setup from one screen
nextDash is a bookmark dashboard that also knows your Docker host. The link to Sonarr, the Sonarr container and the check that watches it are one thing, not three tabs in three different tools.
How it fits together
- Containers — the Containers view (
Shift + Y, #docker) lists every container on the host: a status glow, CPU, RAM, size on disk, ports, its web UI, healthcheck results and a timeline of what happened to it. Start, stop, restart, update, roll back or follow its logs from the keyboard, one container, a compose stack or a whole selection at a time.
- Bookmarks — each container's web UI is matched to the bookmark you already have for it: by port, by subdomain behind a reverse proxy, or by name — or by hand. The container row carries that bookmark's health mark; the bookmark's side panel says which container it runs in. Open the service from the dashboard, from search, or with
:docker sonarr open.
- Health — set that bookmark to Monitor and the server checks it on its own, as often as every five minutes: 30 days of uptime and response times, outages, certificate expiry, a phrase the page must contain, the status codes that count as healthy, and drift when a page turns into something else. A service behind a sign-in can be checked on a status address, with a stored key.
- Alerts and push — a site that goes down and a container that crashes, keeps restarting, turns unhealthy or runs hot reach you the same way: ntfy, Pushover, Gotify, Telegram, Slack, Discord, Apprise, your own JSON receiver, or a push notification on your phone, even with the dashboard closed. Recovery is announced too, and a host that takes ten services down sends one message, not ten.
Keeping it current and tidy. Image update checks run on an interval and show the release notes behind an update. Skip a version, hold a container, or let nextDash update it in a nightly window: each update is watched for five minutes and rolled back when the container stops, loops or turns unhealthy. The Disk tab shows what images, volumes, build cache and bind mounts take up, and clears it after naming what goes.
On the dashboard. A homelab page can carry the Containers and Container list widgets, Uptime, Certificates, Health, Processor, Memory and Disks, seven Unraid widgets (overview, array, parity, shares, VMs, UPS and notifications) that read the server through its API, media widgets for Jellyfin, Emby, Plex, Sonarr, Radarr, Seerr, qBittorrent and SABnzbd — what was added, who is watching, what is coming, what was requested and what is downloading, with the posters from your own library — a Home Assistant widget that switches lights, switches and scenes from the page, four Beszel widgets that show how your other machines are doing, and a Custom widget that reads Sonarr, Plex, Pi-hole, Proxmox, Home Assistant and 36 more services — next to the bookmarks for all of them.
📖 Self-hosted guide in the manual — the set-up in four steps, how the pieces link up, and a morning routine. Setting up the Docker socket is under Containers view below.
Screenshots
Quick Start
Docker Compose (recommended)
services:
nextDash:
image: ghcr.io/jordibrouwer/nextdash:latest
container_name: nextDash
ports:
- "8080:8080"
volumes:
- ./data:/app/data
environment:
- PORT=8080
# On a LAN or VPS, require a token for every write (see Security):
# - NEXTDASH_WRITE_TOKEN=change-me-to-a-long-random-string
restart: unless-stopped
docker compose up -d
Open http://localhost:8080.
From a git checkout: docker-compose.prod.yml is for production (only ./data is mounted; CSS and JavaScript are built into the image). docker-compose.yml is for development (it mounts ./static, ./locales and ./templates, with Docker actions and root off and the socket commented out). Put your own mounts and variables in docker-compose.override.yml; Compose reads it automatically.
docker compose -f docker-compose.prod.yml up -d --build
Build from source
go build -o nextDash && ./nextDash
Data is stored in ./data. NEXTDASH_DATA_DIR moves it.
System widgets
The Processor, Memory, Disks, Containers and Container list widgets report on the machine nextDash runs on. The binary needs no setup; a container needs read-only mounts:
volumes:
- ./data:/app/data
- /mnt:/host/root/mnt:ro,rslave # Disks: required
# - /proc:/host/proc:ro # Processor, Memory: optional
# - /var/run/docker.sock:/var/run/docker.sock:ro # Containers: a real grant
environment:
- NEXTDASH_HOST_ROOT=/host/root
# - NEXTDASH_HOST_PROC=/host/proc
# - NEXTDASH_DOCKER_SOCKET=/var/run/docker.sock
# - NEXTDASH_DOCKER_CONTROL=1 # Containers: start/stop/update/remove
Containers view
[!IMPORTANT]
The Containers view needs three settings before it does anything — and one more on some hosts.
- The Docker socket. Mount
/var/run/docker.sock and set NEXTDASH_DOCKER_SOCKET=/var/run/docker.sock. Without both, the view shows a setup card and the Containers widget stays hidden. Read-only (:ro) is enough to look.
- Actions:
NEXTDASH_DOCKER_CONTROL=1. Start, stop, pause, restart, update and remove need it. Without it the view only reads.
- A write token, and a gate in front:
NEXTDASH_WRITE_TOKEN. Access to the socket is root on the host — :ro on the mount does not stop the Docker API from accepting writes. The token stops other websites and scripts that do not know it. It is not a login: the dashboard hands it to every browser that opens the page. Set one, and keep nextDash behind Tailscale or a reverse proxy with authentication — with actions on, anyone who can open the dashboard can stop, update or remove your containers.
- Sometimes:
NEXTDASH_RUN_AS_ROOT=1. The container starts as root, then drops to its own nextdash user, which joins the group the socket belongs to (docker, gid 281 on Unraid). When the socket belongs to root's group (gid 0) — Docker Desktop, some NAS systems — that user cannot read it: the log says is owned by gid 0 and Config → Containers shows No access to the socket. NEXTDASH_RUN_AS_ROOT=1 keeps the app running as root so it can. Only set it then.
Docker Compose — add to the nextDash service:
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
environment:
- NEXTDASH_DOCKER_SOCKET=/var/run/docker.sock
- NEXTDASH_DOCKER_CONTROL=1 # start/stop/restart/update/remove
- NEXTDASH_WRITE_TOKEN=change-me-to-a-long-random-string
# - NEXTDASH_RUN_AS_ROOT=1 # only if the log says "owned by gid 0"
Unraid — Docker → nextDash → Edit:
- Fill in the template's Docker socket path (
/var/run/docker.sock), Docker socket variable (/var/run/docker.sock) and Write token.
- For actions: set the template's Docker actions to
1 (it starts at 0).
- Unraid's socket belongs to the
docker group, so leave Run as root at 0.
Once it runs, the #docker view lists every container with a status glow, CPU and RAM and a link to its web UI, a side panel with health, a timeline, logs, an hour of CPU and memory charts and release notes, a logs window, a Disk tab, and a badge for images with an update waiting. Config → Containers shows the connection as the server sees it — socket, actions, write token, its own container — and holds the update checks and an optional GitHub token. The manual has the details, including Synology and QNAP.
Unraid
nextDash reads an Unraid server through its own API (Unraid 7.2, or an older Unraid with the Unraid Connect plugin):
- Seven widgets — an overview, the array (every disk with its fill and temperature or its problem), parity, shares by where they live, VMs, the UPS and Unraid's notifications.
- Alerts — Unraid's own ALERT notifications, the array stopping, a parity check that finished with errors and a disk whose error count went up, through the same channels as downtime and container alerts.
- One connection — set once under Config → Unraid with an API key that has the role Viewer. nextDash only reads: it never starts, stops or changes anything on the server.
More is on the way: deeper Unraid integration is being worked on for future versions of nextDash. Manual: Unraid
Security
nextDash is built for personal or small-team use on a trusted network. There are no user accounts: anyone who can reach the address can read and change the data unless you put something in front of it.
Do not expose nextDash directly to the internet. Use one of these:
- A private network — Tailscale or another mesh VPN.
- A reverse proxy with authentication — Traefik, Caddy or nginx with basic auth, OAuth2 Proxy or SSO.
- Local only — bind to
127.0.0.1 and use an SSH tunnel.
The short version is below; MANUAL § 23 has the details.
- Write token. Set
NEXTDASH_WRITE_TOKEN and every write or destructive API call needs the header X-NextDash-Token. The dashboard supplies it for you, which means the page hands it to every browser that opens it. So the token keeps out other websites (a page that fires requests at your network) and scripts that only know the address — not someone who can open the dashboard. Keeping those out is the job of the network or proxy above. Use a long random string, such as openssl rand -hex 32; the server warns at startup when a token is short or still the example value. The capture routes (/add and the share target) cannot send a header; give them NEXTDASH_CAPTURE_TOKEN, which opens capture and nothing else.
- CORS. Only browser extensions receive CORS headers.
NEXTDASH_CORS_ORIGINS allows pages of your own; * allows every origin.
- Outgoing requests. With local bookmarks disallowed, the server only reaches public hosts, re-checks addresses when it connects, and is rate-limited per client.
- The data directory is not served. Only icons and an uploaded favicon or font are public.
- Activity trail. A machine-readable JSON record, with seventeen channels. Changes and check results are on by default; choose the rest under Config → Logs → Activity trail or with
NEXTDASH_ACTIVITY_LOG. URLs and searches can appear in it, so treat the files as private.
- Docker actions. Starting, stopping or updating a container needs
NEXTDASH_DOCKER_CONTROL=1 plus the write token when one is set; reading the container list and running an update check need only the socket.
Production Docker
docker-compose.prod.yml serves CSS and JavaScript from the binary, mounts only ./data, and sets a 256 MB memory limit. The entrypoint starts as root so host Docker hooks can run, then switches to the nextdash user (NEXTDASH_RUN_AS_ROOT=1 keeps root). For TLS and long-cache static serving, run docker compose -f docker-compose.proxy.yml up -d with deploy/Caddyfile.
Recommended LAN/VPS environment:
environment:
- PORT=8080
- NEXTDASH_WRITE_TOKEN=change-me-to-a-long-random-string
- NEXTDASH_CORS_ORIGINS=https://dash.example.com
- NEXTDASH_ACTIVITY_LOG=mutate,status,security
- NEXTDASH_ACTIVITY_LOG_PERSIST=1
# Capture from a bookmarklet, share sheet or script without the write token:
# - NEXTDASH_CAPTURE_TOKEN=a-second-long-random-string
# Automatic backups:
# - NEXTDASH_AUTO_BACKUP_KEEP=7
# - NEXTDASH_AUTO_BACKUP_DIR=/backups # mount a volume there
# Logging:
# - NEXTDASH_LOG_LEVEL=warn
# - NEXTDASH_ACTIVITY_LOG_FORMAT=json # for Loki or Vector
# - NEXTDASH_ACTIVITY_LOG_URLS=host
# - NEXTDASH_ACTIVITY_LOG_MAX_AGE_DAYS=30
# System widgets (see Quick Start):
# - NEXTDASH_HOST_ROOT=/host/root
# - NEXTDASH_DOCKER_SOCKET=/var/run/docker.sock
# - NEXTDASH_DOCKER_CONTROL=1
# Rate limits and headers:
# - NEXTDASH_OUTBOUND_REQUESTS_PER_MIN=120
# - NEXTDASH_SSRF_API_RATE_PER_MIN=60
# - NEXTDASH_STATUS_PING_RATE_PER_MIN=300
# - NEXTDASH_TRUSTED_PROXIES=10.0.0.0/8
# - NEXTDASH_CSP=off
# For everyone on this server:
# - DISABLE_TELEMETRY=true
# - DISABLE_UPDATE_CHECK=true
# - DISABLE_NEWS_FEED=true
Every variable is listed in the reference table below.
GET /version returns the version and commit. GET /api/data-revision returns a hash, so open dashboard tabs notice changes made elsewhere.
Environment variables (reference)
| Variable | Default | Purpose |
|---|
PORT | 8080 | HTTP port (1–65535) |
NEXTDASH_DATA_DIR | ./data | Where pages, bookmarks, settings and uploads live |
NEXTDASH_WRITE_TOKEN | (unset) | Require X-NextDash-Token on writes |
NEXTDASH_ALLOWED_HOSTS | (unset) | With a write token set: extra host names the dashboard may be opened by, comma-separated (*.example.com allowed, * turns the check off). IPs, localhost and private names (.local, .lan, .ts.net, no dots) always pass |
NEXTDASH_CAPTURE_TOKEN | (unset) | A token that opens only /add and the share target |
NEXTDASH_CORS_ORIGINS | (unset) | Extra origins allowed to use the API, comma-separated; * for all. Extensions are always allowed. |
NEXTDASH_CSP | on | off disables the Content-Security-Policy header |
NEXTDASH_OUTBOUND_REQUESTS_PER_MIN | 120 | Rate limit for requests the server makes for you |
NEXTDASH_SSRF_API_RATE_PER_MIN | 60 | Rate limit for the preview, icon, archive, check-URL and alert-test APIs |
NEXTDASH_STATUS_PING_RATE_PER_MIN | 300 | Rate limit for /api/ping, the status checks the dashboard runs in your browser |
NEXTDASH_TRUSTED_PROXIES | (unset) | Addresses and CIDR ranges whose X-Forwarded-For is believed, comma-separated. Unset, the header is ignored and rate limits count per connecting address. |
NEXTDASH_AUTO_BACKUP_KEEP | 3 | How many automatic backups are kept (1–50) |
NEXTDASH_AUTO_BACKUP_DIR | data/auto-backups |
Features
Each line links to the part of the manual that explains it.
Bookmarks and pages
- Pages and categories, each with an icon, a colour and a sort; drag categories and widgets into place — wide across two columns, or onto another page — and spread a category across columns. Share a page as a template file: your own addresses become names the importer fills in. Manual §9
- Edit mode changes the dashboard in place:
Shift + M (or the pencil in the action bar, or Edit in panel… in a category's or widget's menu) puts an outline on every block, a click chooses one, and a panel beside the page edits its name, icon, width, view and sorting, a widget's settings included. Double-click a title to rename it. Manual §4
- Add a link with one key, the full form, a paste, the extension, the share sheet or a bookmarklet — or right-click a category header and choose Add new bookmark, with that category already chosen. Manual §5
- Tags, notes, shortcuts and pins, a preview card that says what a page is without opening it, and a QR code (
Shift + J) to open a bookmark on your phone. Manual §6, §10
- A tag cloud (
/) and a tag view per tag: every bookmark with that tag from every page in one table, with related tags, bulk actions, and rename, merge or remove for the tag. Manual §10
- Tag suggestions tag whole groups at once — from your own tags, a catalogue of some 51,000 sites in 471 subjects, a Wikidata lookup for sites it does not know (only the host name leaves the server, and you can switch it off), and rules you write. The lookup also runs quietly for a link that arrives in the inbox or your bookmarks, and shows what it finds as a chip. They show in the rows of the tag view, the Bookmarks view and the inbox, with . Nothing is tagged until you accept.
Search and keyboard
- Everything is reachable from the keyboard: one rule for the shortcuts and a searchable cheat sheet on
!. Manual §7
- A key legend under the grid keeps the main keys in sight (
Shift + Z switches it off), a dashboard tour of ten steps plays again with Shift + K, a four-step keyboard tour with :tour keyboard, and after an update the What's new window gives the main change of a release a spotlight. Manual §7
- One panel for search, commands and finders, plus search from the browser's address bar. Manual §8
- Usually now puts the bookmarks you tend to open around this time of day at the top of the empty search panel, and
→ on a result unfolds what you can do with it: open, open in a new tab, edit, copy the address, show in the list, move. Manual §8
- Filters for tag, category, page, status, added and opened — each also in the negative. Manual §8.2
Health and monitoring
- Health lives in the Bookmarks view: filters for broken, stale, duplicated, unchecked and changed, a Health tab in the side panel, and Work through to clear a pile — broken, changed, stale, never opened — one bookmark at a time, each with the reason it is there. Collection health (Overview, Monitors, Trend) covers the whole collection; open one bookmark's own Health in Large for its uptime, response time, status codes and every check, with CSV export. Health and monitoring
- Domain expiry. nextDash looks up when the domains of your checked bookmarks run out, through the registries' public RDAP service, and warns at 60, 7 and 3 days — in a Domains widget, as a badge in the Bookmarks view, through your alert channels and in the weekly digest. One request per domain a day; a switch under Config → Monitoring turns it off. Manual §12.4
- Uptime monitoring with 30 days of history, response times, outages, certificate expiry, expected-response checks and drift detection. Manual §11.8
- A checkup walks you through what is worth tidying up — dead links, duplicates, bookmarks nobody opens, empty categories and pages, widgets that show an error — one step at a time, with nothing removed before you have seen it. Type
:checkup. Manual §12
- A status page for the people who use your services: a read-only page behind a secret link with your groups of services, whether each one works, since when one is down, planned maintenance and 30 days of history. It shows no error details or internal addresses, refreshes itself every minute and follows the visitor’s language and light or dark. Manual §12.8
- Alerts, set under Config → Monitoring (tabs Checks, Notifications and Schedules), to Slack, Discord, Telegram, Gotify, ntfy, Pushover, Apprise (and from there mail, Matrix, Signal and a hundred more), a JSON receiver or your browser, with maintenance windows, quiet hours with one summary at the end, reminders for an outage that goes on, per-bookmark muting, and a weekly digest of what broke, what can be updated and what nobody opens.
Widgets
- Forty-eight kinds: health, uptime, certificates, domains (registrations about to run out), trend, inbox, Unsorted, feeds, sources, neglected, blind spots, duplicates, archive, trash, backups, processor, memory, disks, containers, container list, weather, calendar, RSS, Notes (Markdown with checkboxes and slash commands), and seven that read an Unraid server through its API — an overview, the array, parity, shares, VMs, UPS and its notifications — set up once under Config → Unraid, eleven media widgets: Jellyfin, Emby and Plex (what was added lately; Plex is read through Tautulli), each with a now playing tile that shows who is watching what, Sonarr and Radarr (what is coming and in the queue), Seerr (requests), and qBittorrent and SABnzbd (downloads), with posters where there are any, a Home Assistant widget, four Beszel widgets that read a Beszel hub — every system, one system in full, only the systems that need a look, and every disk — and a Glances widget for one host, as three meters or the processor's last hour. A row on the Unsorted or containers widget opens the Bookmarks or Containers view on it. Manual §15
- A widget set to two columns says more rather than the same thing larger: the load behind the processor's percentage, the container failing by name, the expiry date of a certificate, what the weather feels like. One column keeps the important half. Manual §15.2
- A Custom widget reads any service that answers with JSON, with 41 self-hosted services filled in — Sonarr, Plex, Pi-hole, Proxmox, Home Assistant, Uptime Kuma, Beszel and more — each tested against the service's recorded answer. Manual §15.5
Containers and your homelab
- A Containers view (
#docker, Shift + Y) for everything on the host: a status glow that is red only for a failure, links that grey out for a container that is not running, sortable columns with CPU, RAM and each container's size on disk, group by status or compose project, a web UI column, and a side panel with health checks, a timeline of what happened, stats, an hour of CPU and memory charts and environment. Give any container a web UI address of your own; the list, the widget and :docker <name> open all use it. Containers view
- A Glances page (
Shift + G) for the machines you run Glances 4 on: processor, memory, disks, processes and containers now, and a record of its own — thirty days of graphs, incidents drawn as red bands, a forecast for disks that fill up, a comparison with last week, and Insights that answer from the record — a health score, a typical day, the load against the cores, where the memory goes and who used the most, with an info button on every block. Up to five hosts, a widget for the dashboard, notices through your alert channels, and a link both ways with the Containers view, which can read its CPU, memory and network from Glances. nextDash only reads. Manual §15A
- Start, stop, pause, restart, update and remove — one container, a whole compose stack, or every container you tick — behind
NEXTDASH_DOCKER_CONTROL and the write token; set it all under Config → Containers. Containers view
- Image update checks, on request and on an interval, show what changed; skip a version, hold a container's updates, watch an update's steps and log while it runs, see what updates did and roll the last one back. The header icon carries a badge for how many are waiting. Containers view
- A logs window that follows a container's log live, a Disk tab for what images, volumes and the build cache take up, and notices when a container stops, keeps restarting or turns unhealthy.
Appearance
- 192 theme families in light and dark, each on a material that decides how its surfaces are drawn — lacquer, glass, velvet, terminal and more — with a signature or Classic way to draw it, eight neutrals with one accent, ThinkDashboard Classic and an editor for your own. Aurora Glass is the default, and every install moved onto it once. Manual §16
- A theme studio beside the dashboard. It opens beside the dashboard and changes the page live: the theme, its backdrop, depth and card glass, the category headers and the type. Twelve ready-made looks set them in one go; Compare shows what you had, and nothing is saved until Apply. Theme studio
- 75 backdrops, from aurora and dunes to stars and hexagons, each material with a pool of its own and each theme with one picked for it — or choose your own and tune it with intensity, scale, blur, tint and a quiet centre. Manual §16.4
- Character, depth, glow, effects, card glass and contrast for any theme; category header styles, layout presets, columns, density and fonts. Manual §16.3
- A header you arrange yourself: four page-switcher styles, and action buttons in a dock, a side column, the header or one menu, in five sizes. Manual §4
- Appearance in nine tabs, three groups. Panels fold to a line of their values, runs of switches are chips, and a list of panels sits above the preview on long tabs. Manual §16
- The dashboard reads in Source Code Pro and every other screen in Inter; a theme or look can name another typeface. Manual §16.4
- Six languages: English, Dutch, German, French, Spanish and Chinese.
Data
- Import the bookmark file every browser exports — and Pocket, Pinboard, Raindrop, linkding, Shiori, Linkwarden and Karakeep — plus CSV. Export to HTML and CSV. Manual §19.1
- Sources keep bookmarks arriving from GitHub stars, Raindrop.io, Hacker News, YouTube and Mastodon. Manual §19.2
- Automatic backups of the whole data directory, and a 30-day trash. Manual §19
- A server log and an activity trail in the app. Manual §20
Self-hosting
- One Go binary and a directory of plain JSON. No database, no accounts, analytics only if you switch them on, and a daily install count (a random id and the version, nothing else) that you can turn off. Manual §23
- A write token, a CORS allowlist, rate limits, SSRF protection and an activity trail for when it faces a network. Security
What nextDash talks to
- Browser extension (
extension/) — saves the current tab to a page or to the inbox. Open chrome://extensions/, switch on Developer mode, click Load unpacked and choose the extension/ folder. Manual §21
- A capture route —
GET /add?url=…&title=… saves to the inbox and answers with a readable page, so anything that can open a URL or run curl can save to nextDash. Manual §21.2
integrations/ — a shell one-liner, two Raycast commands, a Dropzone 5 action, a Ulauncher extension, and recipes for Alfred and Apple Shortcuts, all built on that route. The Dropzone 5 action also has its own repository. integrations/README.md- A bookmarklet and the phone share sheet — Config → Help → Inbox builds a bookmarklet for your install; installed as an app, nextDash joins the share sheet. Manual §22
- Outgoing webhooks — seven events, signed with the Standard Webhooks scheme. Manual §19.3
- An MCP endpoint — four tools for MCP clients to search and add bookmarks, off until you switch it on. Manual §23.6
Contributing
Issues and pull requests are welcome — bugs, features and translations alike.
Branch workflow
| Branch | Purpose |
|---|
dev | Day-to-day development (tests, CI, scripts) |
main | The published release, for Docker and the public repository page |
-
Branch from dev and open pull requests into dev.
-
CI runs on pushes and pull requests to dev.
-
When a release is ready, merge dev → main with:
git checkout dev
./scripts/release-to-main.sh v1.11.0
The script merges, removes development-only files from main (tests, Playwright, internal scripts), tags the release, pushes, and publishes a GitHub Release with gh. One-time setup: brew install gh and gh auth login.
Do not merge dev into main by hand on GitHub.
Clone for development: git clone, then git checkout dev.
Clone for Docker or stable use: stay on the default main branch.
License
MIT
