Stewer is the command‐line launcher for Divooka graphs. It enables you to run any Divooka graph definition (a .dvk file or legacy .Parcel file) directly from a terminal, script, CI/CD pipeline, or operating-system scheduler - without opening the Divooka graph editor. Stewer loads the specified graph, feeds any provided inputs, and returns a standard exit code (0 on success, non‐zero on failure).
Bundled with Divooka
Stewer is included in all standard Divooka distributions (for example, Divooka Explore). After installing Divooka, the stew executable will be available in your installation’s root directory.
Docker Hub
If you prefer to run Stewer in a containerized environment, you can pull the official image from Docker Hub:
docker pull methodox/stew
Once pulled, you can invoke Stewer via:
docker run --rm -v /path/to/graphs:/graphs methodox/stew stew /graphs/MyGraph.dvk
The simplest way to run a Divooka graph is:
stew <GraphPath> [<GraphInputs>]
<GraphPath>
The filesystem path to your graph definition, for example Graphs/ImportSalesData.dvk or projects/MyWorkflow.Parcel.
<GraphInputs> (optional)
Positional arguments that correspond to input‐type nodes defined in the graph. For instance, if your graph expects a single string (e.g., a CSV file path), you might run:
stew Graphs/ImportSalesData.dvk "C:\Data\sales_2025_06_01.csv"
If no inputs are required by the graph, you can omit the [<GraphInputs>] section entirely.
Running stew --help displays the global usage and options:
usage: stew <GraphPath> [<GraphInputs>]
Global options:
--help Show this help message and exit
--version Print Stewer version and exit
--log-level <level> Set logging level (e.g., DEBUG, INFO, WARN, ERROR)
--config <file> Path to a custom Stewer configuration file
To get detailed help for a specific graph (including a list of its input nodes, types, and default values), use:
stew --help <GraphPath>
For example:
stew --help Graphs/ImportSalesData.dvk
This command will print a summary of all named input parameters (their data types and any defaults), which makes it easy to script against complex graphs without manually inspecting the .dvk file.
When you execute:
stew --help <GraphPath>
Stewer parses the graph definition and prints a list of input nodes in this format:
Graph: ImportSalesData.dvk
Inputs:
1. csv_file_path (string, required) – Path to the CSV file to import.
2. batch_size (integer, optional, 100) – Number of rows to process per batch.
3. debug_mode (boolean, optional, false) – Enable verbose logging.
By knowing this signature, you can build wrapper scripts that validate or transform input values before calling Stewer.
Stewer follows standard UNIX conventions for exit codes:
0 – Graph executed successfully; all nodes completed without errors.You can check $? (on UNIX‐like systems) or %LASTEXITCODE% (in PowerShell) immediately after invocation to detect failures and trigger appropriate error handling.