Understanding NasDash

Architecture and Data

Understanding containers, API routes, and files to protect.

Overview

Browser
   | HTTPS or private HTTP
   v
Optional reverse proxy
   |
   v
NasDash / Next.js :2504
   +-- /app/data                         persistent store
   +-- Glances / Netdata / Beszel / Prometheus / Proxmox / LHM
   +-- Tailscale / Headscale
   +-- Docker / Portainer / Dockhand connections
   +-- docker-socket-proxy :2375         restricted Docker API
          +-- /var/run/docker.sock:ro

Browser --> Open-Meteo                  weather and location search

The :ro mount of the socket prevents the proxy from modifying the socket file itself. The allowed operations remain determined by the proxy variables (POST, DELETE, etc.).

Persistent Files

FileRole
config.jsonSettings, shared integrations, machines, hosts and actions
services.jsonCategories and services
topology.jsonNodes, groups and connections
calendar.jsonLocal events
custom_tabs.jsonLegacy custom tabs and layouts
users.jsonAccounts, hashes, roles and session versions
jwt.secretPersistent signing key when no environment override is provided
encryption.keyPersistent encryption key when no environment override is provided
logos/Uploaded logos
pages.jsonComposable pages, layouts and mobile preferences
metrics-history.jsonPersisted machine metric history
backups/Local archives; download copies off-host

Operational Constraints

  • Use a single NasDash instance per data store.
  • Do not mount /app/data as read-only in normal production.
  • Back up the entire folder or volume, including keys.
  • Never place the actual contents of data/ in Git.
  • A serverless platform is suitable for stateless demos, not for persistent self-hosted instances.

Container Process

The production image is built with Node.js 22 Alpine and runs the application under UID/GID 1001:1001. The health check queries http://127.0.0.1:2504/api/health.