You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After downloading the blueprint #158 it should be ready to be executed, each blueprint would expect to be executed with a set of env variables that are set by the manager for the child process (or remote process):
RPC_URL: The remote RPC url for tangle
KEYSTORE_URI: the keystore file where the keys are stored and could be retrieved.
DATA_DIR: is an isolated path for where this gadget should store its data (database, secrets, …etc)
BLUEPRINT_ID: the active blueprint ID for this gadget
SERVICE_ID: the active service ID for this gadget
HEALTHCHECK: If set, the gadget just prints its version and exist with a status code zero, to check if the binary is configured correctly.
Once it starts, the child process or the remote process should be kept alive, and monitored by the shell manager. If it fails or panicked, the shell manager should report the issue to the operator and depends on the configuration, the gadget may need to be restarted again.
The text was updated successfully, but these errors were encountered:
After downloading the blueprint #158 it should be ready to be executed, each blueprint would expect to be executed with a set of env variables that are set by the manager for the child process (or remote process):
RPC_URL
: The remote RPC url for tangleKEYSTORE_URI
: the keystore file where the keys are stored and could be retrieved.DATA_DIR
: is an isolated path for where this gadget should store its data (database, secrets, …etc)BLUEPRINT_ID
: the active blueprint ID for this gadgetSERVICE_ID
: the active service ID for this gadgetHEALTHCHECK
: If set, the gadget just prints its version and exist with a status code zero, to check if the binary is configured correctly.Once it starts, the child process or the remote process should be kept alive, and monitored by the shell manager. If it fails or panicked, the shell manager should report the issue to the operator and depends on the configuration, the gadget may need to be restarted again.
The text was updated successfully, but these errors were encountered: