Solves #78. Also includes fixes for the inconsistent usage of environmental variables.
A premade collection of discovered devices as well as created modules and deployment manifests can be initialized to the database when the orchestrator is started.
The initialization data is put into the local ./init folder, which is shared with the orchestrator container.
Instructions on how to create the initialization data have been added to the repository readme.
Fixed IP addresses within the wasm-iot Docker network for the orchestrator and the example devices have been added to have deployments that will not break after restart.
Solves #78. Also includes fixes for the inconsistent usage of environmental variables.
A premade collection of discovered devices as well as created modules and deployment manifests can be initialized to the database when the orchestrator is started.
The initialization data is put into the local
./initfolder, which is shared with the orchestrator container. Instructions on how to create the initialization data have been added to the repository readme.Fixed IP addresses within the
wasm-iotDocker network for the orchestrator and the example devices have been added to have deployments that will not break after restart.Only tested with the example Docker devices.