Configure dig-node
A dig-node runs headless with sensible defaults; you tune it through its config file and DIGNODE_* environment variables.
What you can set
| Setting | What it controls |
|---|---|
| Listeners / ports | The address and port the dig RPC is served on (and dig.local resolution). |
| Cache cap | The maximum on-disk size of the .dig cache (a set of capsules); the node evicts to stay under it. |
| Upstream | The remote the node blind-fetches ciphertext + proofs from when it doesn't have a capsule cached (defaults to the public network). |
| Relay | The relay the node keeps a constant connection to so peers behind NAT can reach it — defaults to the public relay.dig.net. Override with DIG_RELAY_URL (e.g. point at your own relay); set DIG_RELAY_URL=off to disable it (air-gapped nodes). See Run a relay. |
The node only ever stores and relays ciphertext keyed by hashes — configuration never changes the blind serving contract. A capsule it doesn't have is fetched from the upstream, verified, and cached.
Apply settings
Set values in the config file or as DIGNODE_* environment variables (env overrides file). After changing settings, restart the node:
dign stop && dign start
That works on every platform and every install route. To drive the service manager directly instead, use the id for your route — see finding the service on your machine.
Related
- Install anywhere — the universal installer
- Run a relay — how a node stays reachable behind NAT, and how to run your own relay
- Manage your node — control.* admin RPCs
- Node conformance — the blind serving contract