Operate distributed nodes without exposing every system

Operating distributed nodes across private networks can create its own management burden. nyssr.net is more than a message transport: its surrounding services provide operational capabilities for configuring, updating, and coordinating a node network.

Configuration from the network

A node can retrieve configuration from another node during startup. This keeps the executable generic while allowing each deployment to define its own plugin set and role.

FileStores move artifacts locally

FileStore services provide files from a directory or memory store to other services. Files can be requested by name or hash and delivered to the local FileStore of the requesting node.

This supports redundant file distribution and shorter transport paths. Software updates use FileStores for JARs; RemoteSkin can use them for icons and other UI assets.

Remote console access

Each node includes a console for status information and commands. It can be accessed from another node even when nodes are behind firewalls or running in containers, as long as a reachable local node is available.

Controlled software updates

A local control file can describe the libraries, plugins, and kernel version a node should use. The configuration is transferred to affected nodes, which retrieve the required JARs through FileStores, load the new plugin set, and restart.

Hashes and timestamps help distinguish identical files from newer versions.

Key idea: Operate remote nodes through messages and control files instead of exposing every node directly.

Coordinated reboot and applications

Nodes can be rebooted individually, in groups, or across the network at a scheduled time. Applications can be started and stopped at runtime; each instance runs in its own namespace and can be resolved through an application registry.

Automatic load balancing allows the same application to run on multiple nodes.

RemoteSkin integration

RemoteSkin distributes UI behavior across nodes. A client receives a UI description and sends user events back to the application through the node network. Web-based variants use a WebSocket connection to communicate with server-side UI services.

This makes the UI another set of services that can be placed, scaled, and updated independently.

Configuration: Define node capabilities through remote configuration and plugin lists.

Operations: Use console access, FileStores, updates, and controlled restarts without opening every node to the outside.

Applications: Start many isolated instances and resolve them through the service registry.