exred_node_redis_in v0.2.1 Exred.Node.RedisIn
A Redis input node.
Select the Redis command in the config tab.
Expects command arguments in msg.payload either as a list or a string if there’s only one argument.
Examples:
GET command: msg.payload = [“myKey”] OR msg.payload = “myKey”
LRANGE command: msg.payload = [0, 9]
Link to this section Summary
Functions
Returns a specification to start this module under a supervisor
daemon_child_specs/1 needs to return a list of child specs. These child processes will be started under the DaemonNodeSupervisor
fire/1 is called when the user clicks on the play button on a node in the UI (and with that triggers a ‘fire’ event). It should return a new_state
node_init/1 initializes the node process. This is called as the last step of the node’s init function. Needs to return a new state or a {state, timeout} tuple. (see GenServer documentation)
Link to this section Functions
Returns a specification to start this module under a supervisor.
See Supervisor.
daemon_child_specs/1 needs to return a list of child specs. These child processes will be started under the DaemonNodeSupervisor.
Callback implementation for Exred.NodePrototype.daemon_child_specs/1.
fire/1 is called when the user clicks on the play button on a node in the UI (and with that triggers a ‘fire’ event). It should return a new_state.
Since this has access to the node’s state it can be used to implement user triggered actions like logging the state, sending messages from the node or creating debug events that are displayed in the debug tab in the UI.
For an example of how to use it see the Trigger node.
Callback implementation for Exred.NodePrototype.fire/1.
node_init/1 initializes the node process. This is called as the last step of the node’s init function. Needs to return a new state or a {state, timeout} tuple. (see GenServer documentation)
Callback implementation for Exred.NodePrototype.node_init/1.