Getting Started

Possible Configuration Sources

Device configuration data can be supplied to BOSS from various sources.

For a production setup, we recommend using a network based database like CouchDB. This has the advantage, that all configurations are at a central point and are easy to maintain.

python -m boss.starter -u http://<user>:<pw>@<couchdb_host>:5984/my-boss/http-test

See CouchDB for more details.

Hint

BOSS uses urllib to parse the url specified by the -u argument, which supports many more url schemes than listed here. This means you can use also completely different endpoints to host your configuration for BOSS like ftp or svn, the only requirement is that there is a valid JSON configuration string at the end.

Installing/Deploying BOSS

A convenient way to deploy BOSS is inside of a docker container. You can find pre-build containers images in our docker registry.

Hint

You can also build the BOSS docker image yourself from the Dockerfile in the repository: docker build -t atomiq/boss . By building the docker image yourself, you can modify the docker image and add for example custom device vendor libraries or similar.

A BOSS docker service can be started with the following compose file

services:
  httpclient:
    image: registry.gitlab.com/atomiq-project/boss:latest
    restart: always
    network_mode: host
    environment:
     - |
       BOSS1=
       {
        "_id": "docker-env-ftp",
           "classname": "ftplib.FTP",
           "arguments": {
                "host": "ftp.us.debian.org"
           }
       }
    command: python -m boss.starter -e BOSS1

Additionally, also specifying a file or URL is possible, such that (mounted) json files in the docker container or web URLs can be used as configuration sources. Note that the -e and -u options can be specified in the command line multiple times to define several objects that should be instantiated by the BOSS.