Skip to content

daemon

Usage: soup-daemon [OPTIONS] --db-path <DB_PATH> --blob-path <BLOB_PATH>

Options:
  -H, --host <HOST>
      --db-path <DB_PATH>
      --blob-path <BLOB_PATH>
  -h, --help                   Print help

Danger

If you do not supply a -H options, soup-daemon will not be reachable via any options.

Socket Options

Under Unix systems (such as macOS and Linux) soupd defaults to the unix:// protocol, which is a local communication layer. It is file based, so you can apply permissions which users can access the socket via normal unix groups and file permissions.

If you wish to make soupd reachable over the network, you will need to switch to the tcp:// protocol.

Tip

On Unix Platforms its possible to mix unix:// and tcp://

Warning

Windows Builds of soup do not support unix://

The -H options accepts arguments in the following format:

tcp://host:[port] or unix://path

Tls

Since: asd

The functionality described in this section requires version asd of soup, or a more recent version.

passing --tlskey and --tlscert to the launch arguments will activate TLS Encryption on the socket. This only works for tcp:// sockets, as they are the only ones expected to traverse the network.

Secure the unix:// socket using UNIX permissions.

Soup accepts certs in .pem format.

Notice

Enabling TLS, means all tcp:// sockets run TLS and TLS only. soupd does not support hybrid configurations.

Should you need a more advanced TLS configuration, consider puttin soupd behind a proxy

Examples

  • tcp://host:7070 listen for connections on host on port 7070
  • unix:///path/to/file listen for connections on socket path

You can provide -H multiple times to listen on multiple sockets.

soup-daemon -H tcp://127.0.0.1:7070 -H unix:///var/run/soup.sock