netget

local.netget

local.netget is the operator surface for the local NetGet gateway. It is the management interface — where you configure routing, inspect the monad mesh, view logs, and control the gateway.

It is not a user-facing surface. It is the surface from which you manage all other surfaces.


What it is

When NetGet is running and OpenResty is configured, local.netget resolves to the NetGet Dashboard app. The same address is also reachable as localhost and 127.0.0.1.

Address Resolves to
local.netget NetGet Dashboard
localhost NetGet Dashboard
127.0.0.1 NetGet Dashboard

The dashboard is served either from a static build (default) or proxied from a local Vite dev server (dev mode).


What it does

From local.netget you can:


How it is served

NetGet reads ~/.get/xConfig.json to decide how to serve the frontend:

Mode What happens
package-dist Serves the built UI bundled with the installed netget package
local-dist Serves a locally built UI from ~/.get/dist/
dev Proxies all requests to a Vite dev server (default http://127.0.0.1:5173)

To change mode, use the NetGet CLI:

netget → NetGetX → Main Server UI → [select mode]

Or edit ~/.get/xConfig.json directly and regenerate the nginx config.


Dev mode

In dev mode, OpenResty proxies local.netget directly to the Vite dev server. This means:

# In the frontend_local directory
npm run dev

# Then regenerate and reload nginx via the NetGet CLI
netget → NetGetX → Main Server UI → Use Dev React App

The frontend app

The dashboard app that runs at local.netget is built with this.gui. It lives at:

netget/Typescript/src/htmls/Netget-REACT/frontend_local/

It connects to the NetGet Express server (default port 3432) for all API calls — domain management, log streaming, gateway identity, and monad discovery.


Open local.netget

If NetGet is running on this machine, this link opens the dashboard:

🖥️  http://local.netget

Page doesn’t load? → Installing NetGet


See also