Please enhance the bosnd.yml configuration file by adding the ability to define the needed Docker CA certificate, client certificate & client key separately.
For now one can only configure the folder from which the certificates will be used

Now available:

swarm:
  certificate: /bosnd/certs

What would be cool for the new feature/enhancement:

swarm:
  cacertpem: /docker/certs/ca.pem
  clientcertpem: /docker/certs/client-cert.pem
  clientkeypem: /docker/certs/client-key.pem

Thx! :)

For some projects one won't need the dynamic configuration but wants to get the auto-reload on config-change.
Would be nice to get that feature so that bosn'd starts without the Docker swarm configuration in the bosnd.yml configuration file.

It would be helpful to display a version info. Example:

./bosnd -version
Version: v0.2
Codename:  HMS Royal Prince (1663)

The warn messages should include an information about which file is missing, for example.

Extend the configuration possibilities to allow the use of the localhost (or other host) Docker swarm interface without TLS usage. This will be more insecure but will give the possibility to run the Bosnd with PWD Docker for demo purpose.