KNoT Cloud is a cloud computing solution that enables operating on IoT devices by providing a minimum messaging and management infrastructure. It includes device and authentication management services as well as APIs for sending commands to the things and collect data from their sensors. Also, the KNoT Cloud uses some services from the Mainflux platform, which is a lightweight platform for running IoT cloud computing on the edge. Please, check out the official documentation for more information.
Stacks for development and production environments are provided in order to assist the user's needs. The development stack must be used if one needs to modify any of the components of the stack. A command line tool will download the source for each component and plug it into the containers, which all have hot reload enabled. The production stack must be used in all other cases.
If you intend to use the development stack, a command line tool that downloads and configures the stack is required.
npm install -g @cesarbr/knot-cloudThe development stack must be created using the tool described in the previous section. Choose a <path> where the stack should be created (defaults to the current directory) and then run:
NOTE: The following command assumes you don't have a workspace with the repositories and clone them. To disable this, run it with the
--no-cloneflag.
knot-cloud init [path]The source code and stack template files will be created under <path>/stack.
There are two production deployment strategies: all-in-one and multinode. The former will deploy all the services on a single machine while the latter will deploy them in multiple nodes (at least two). The files for the two flavours are available at stacks/cloud/prod. The file multi-node.yml can be added to the deploy command if you want to enable the multinode strategy.
In your deployment machine, initialize Docker Swarm mode:
docker swarm initIn case you are deploying to multiple nodes, all the nodes must be connected to the same swarm. In this case, run the command above in the machine that must be the swarm manager and run docker swarm join in all other nodes, as instructed by the execution of docker swarm init in the manager machine. Check the Docker Swarm documentation for more on how to setup your cluster.
After this point, follow the specific instructions to configure and deploy the created stack:
If you want to stop your stack from running or even leave the Docker Swarm mode, execute the commands below:
docker stack rm knot-cloud
and
docker swarm leave