From 08709730ab70e721eaba222fcd561a87d22ab640 Mon Sep 17 00:00:00 2001 From: Michael Taylor Date: Thu, 9 Jul 2026 22:48:04 -0700 Subject: [PATCH] docs(run-a-node): document dig-node auto-start service + post-install health check dig-installer (v0.4.0) now runs a post-install RPC health check after registering the dig-node service, in addition to the existing dig.local resolve check, and the service already registers as auto-start (all 3 OSes) with auto-restart-on-crash on Linux/macOS. Document this on the universal installer page so users know the install verifies itself, and that the extension/DIG Browser find the node automatically once it's confirmed up. Materialized identically into all 13 locale copies (this page has not yet been translated per-locale, matching every other section already there). --- docs/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ .../current/run-a-node/universal-installer.md | 20 +++++++++++++++++++ package.json | 2 +- 15 files changed, 281 insertions(+), 1 deletion(-) diff --git a/docs/run-a-node/universal-installer.md b/docs/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/docs/run-a-node/universal-installer.md +++ b/docs/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/de/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/es/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/fr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/hi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/hi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/hi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/hi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/id/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/id/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/id/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/id/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/ja/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/ko/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/ru/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/tr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/vi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md index a15030f..4e9d876 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md @@ -33,6 +33,26 @@ The installer registers **`dig.local`** for your machine so consumers on the sam The hosted installers (`apt.dig.net`, `dig.net/install.sh`) are still being provisioned. Until they're live, build from source or grab a binary from the [dig-node Releases](https://github.com/DIG-Network/dig-node/releases). The commands here are the real, intended ones. ::: +## An always-on service, verified after install + +`--with-dig-node` registers `dig-node` as an **auto-start** service — it comes up again after a reboot with no manual step, and starts as part of installation. On Linux and macOS it also **auto-restarts if it ever crashes** (Windows recovery-on-crash is still being wired up). + +Once the service is started, the installer runs two checks and prints the result of each: + +- **`dig.local` resolves** — the OS resolver actually maps `dig.local` to your node's loopback address right now (not just that the hosts entry was written). +- **Health check** — the node answers a live RPC call on its configured port (default `9778`), proving the service isn't just registered but actually serving. + +```sh +dig-installer --with-dig-node +# Registering dig-node as an OS service (port 9778): +# ✓ dig-node installed as an OS service and started +# ✓ dig.local: 127.0.0.2 dig.local → /etc/hosts +# ✓ dig.local resolve check: dig.local → 127.0.0.2 +# ✓ health check: rpc.discover on http://127.0.0.1:9778/ answered +``` + +With the node up and verified, the [extension](../audiences/content-consumers.md) and the [DIG Browser](../browser/chia-protocol.md) find it automatically at `dig.local` (or `localhost:9778`) — no configuration needed on the consumer side. `--uninstall-dig-node` removes the service and the `dig.local` entry cleanly. + ## Browse `.dig` names directly {#browse-dig-names-directly} Add `--with-dig-dns` to also install [`dig-dns`](https://github.com/DIG-Network/dig-dns) diff --git a/package.json b/package.json index 7ad2869..c41e2e3 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "docs-dig-net", - "version": "0.3.11", + "version": "0.3.12", "private": true, "scripts": { "docusaurus": "docusaurus",