2.5 Runtime Module Configuration

FILENAME: runtime-module.cfg

The runtime module configuration file only has one line that needs to be changed:

  • docker.image = NAME_OF_MODULE This should be the name of the docker image of the module. Hence, when the module is run, it will look for that specific docker image. Good practice would be to use different names when the module is updated NAME_OF_MODULE-v2 or include a tag, such as stable or latest.
#  Module configuration file for local execution of modules
runtime.platforms = command

#  Module configuration file for local execution of modules
module_enabled = True
runtime.platforms=command

[command]
docker.image = NAME_OF_MODULE
environments = Staged,Docker
executable = python PythonScriptWrapper.py
files = pydist, PythonScriptWrapper.py

Example. Composite Strength Module

In this example, we see that the name of the docker image is predict_strength. So, when a user hits Run on the Composite Strength module page, BisQue will always pull the latest image of predict_strength.

#  Module configuration file for local execution of modules
runtime.platforms = command

#  Module configuration file for local execution of modules
module_enabled = True
runtime.platforms=command

[command]
docker.image = predict_strength
environments = Staged,Docker
executable = python PythonScriptWrapper.py
files = pydist, PythonScriptWrapper.py