Andrew Ferrazzutti
27b2c15ad3
- Move config from Python to Node - Also log responses - Only log request/response object properties in Node, as logging them in both Node and Python is redundant - Error-out if Node listen config is missing - For convenience, make PeerClient copy setting properties from ClientManager instead of referencing them |
||
|---|---|---|
| .. | ||
| src | ||
| .dockerignore | ||
| .gitignore | ||
| Dockerfile | ||
| README.md | ||
| docker-run.sh | ||
| example-config-docker.json | ||
| example-config.json | ||
| package-lock.json | ||
| package.json | ||
README.md
Listen config
If type is unix, path is the path where to create the socket, and force is whether to overwrite the socket file if it already exists.
If type is tcp, port and host are the host/port where to listen.
Register timeout config
register_timeout is the amount of time (in milliseconds) that a connecting peer must send a "register" command after initiating a connection.
Logging config
logging_keys specifies which properties of RPC request & response objects to print in logs. Optional.