Documentation
¶
Overview ¶
Operating a node.
The service is a value with a registry of typed operations on it — see ops.go, which is where every operation and its doc live. This file is the value: what the service is built from, what it holds, and the two things more than one operation needs.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type ChainTracker ¶
ChainTracker is the interface for tracking chains at runtime.
type Config ¶
type Config struct {
Log log.Logger
ProfileDir string
LogFactory log.Factory
// NodeConfig is the configuration this node booted with. It is the node's
// own type rather than an `any` because an operation's reply is its type:
// an untyped one has no schema, no MCP shape and no generated client. What
// may be DISCLOSED of it is a separate question with its own answer —
// `json:"-"` on the fields that hold key material, in config/node.
NodeConfig *nodeconfig.Config
DB database.Database
ChainManager chains.Manager
HTTPServer server.PathAdderWithReadLock
VMRegistry registry.VMRegistry
VMManager vms.Manager
PluginDir string
Network ChainTracker
// DataDir is the node's data directory, used for backup metadata.
DataDir string
}
type Service ¶
type Service struct {
Config
// contains filtered or unexported fields
}
Service is the node's operator API. Its operations are registered by Service.Ops.
Click to show internal directories.
Click to hide internal directories.