Whisperers as standalone executables

Since their rewrite in Go under the Gossiper binaries, Whisperers may also be run as standalone executables.

Gossiper releases are listed in the Changelog.

Command

In this case, you need to have a Linux system with a compatible libc version, and you launch a Whisperer with a simple command line.

gossiper

Configuration

Whisperers require a configuration file in JSON to run and contact Spider server.
Once this initial step is done the whole configuration is managed by the UI and downloaded by the Whisperer.

The configuration file is generated on the UI as described before and given to the Whisperer either by environment variable or as a file config.json in current path.

Dependencies

Released Gossipers require libc to run.
If needed, a specific libc version or a musl version could be packaged. Ask support.

Whisperer options

Options may be defined from environment variables:

Name (*: mandatory)	Description	Default
CONFIG *	JSON configuration value for the Whisperer. By default, reads the file ./config.json in the current path.
LOG_LEVEL	Define the log level. May be FATAL, ERROR, WARN, INFO, DEBUG, TRACE	INFO
HOSTNAME or PARENT_HOSTNAME	Sent back to the server in the hostname field of status. Used for proper identification in the UI.
INSTANCE_ID	Used to differentiate replicas of a same Whisperer. Must be unique by Whisperer.	os.hostname()
DNSCACHE_HOST	Used to force a DNS server. Even to connect to Spider server. Specifies its hostname or IP.
DNSCACHE_PORT	Used to force a DNS server. Even to connect to Spider server. Specifies its port.	53
CAPTURE_OWN_COMS	If set - whatever value that resolve to true -, the Whisperer will also capture its communications to Spider. DANGEROUS!