Completion Scripts

When a task finishes — successfully or with an error — Risuko can fire a configurable script. Use it to upload to a server, send a notification, trigger a transcoder, or update an external database.

[!INFO] Completion scripts are a desktop-app feature wired through the run_completion_script Tauri command. The CLI serve mode does not currently invoke them — use the Cloud Upload Sinks subsystem for headless post-processing.

Configuration

The relevant keys live in user.json (or Preferences → Advanced in the desktop app):

The script is executed directly, not through a shell. Each whitespace- separated token in the args template becomes one argv entry, so quoting, shell expansions, and pipes are not interpreted — a single argument can never contain whitespace. If you need shell features, wrap the pipeline in a dedicated shell script and point completion-script-command at it.

The Test script button in the same pane runs the configured command once with sample values (/tmp/risuko-test-file, an all-zero hash, status complete) so you can validate it without waiting for a real download.

Placeholders

Both the args template and the spawned environment expose:

Placeholders are substituted inside each argv token after splitting, so --file={path} produces a single argument like --file=/downloads/foo.zip. {path} is substituted last, so placeholder-looking text inside the file path is never re-expanded.

Per-Task Overrides

Individual tasks can override the global settings from the Add Task dialog's advanced options. The overrides are stored as task option keys — risuko-completion-script-command, risuko-completion-script-args, risuko-completion-script-timeout-ms, and risuko-completion-script-enabled — which the app reads back when the task finishes. Notably:

• Setting a per-task command implicitly enables the script for that task, even when the global switch is off — unless the override also sets risuko-completion-script-enabled: false explicitly.
• risuko-completion-script-enabled: false always wins, useful for opting one noisy task out of the global script. The Add Task dialog writes it automatically when the override toggle is on but no command is given.
• Timeout overrides are clamped to the same 1000–300000 ms range.

Output Handling

The run is fire-and-forget: it logs a one-line summary at info on success or warn on a non-zero exit, spawn failure, or timeout. The failure line includes the captured stderr; stdout is not logged. Both streams are captured and truncated to 8 KiB with a ...[truncated] marker — the Test script button returns the full captured stdout and stderr to the UI. Scripts that run past completion-script-timeout-ms are reported with timed_out: true; Risuko stops waiting for them but does not kill the process.

Example: Notify via terminal-notifier

Command: /usr/local/bin/terminal-notifier
Args:    -title Risuko -subtitle {status} -message {path}

Example: Move to a NAS via rsync

Because the args template cannot express an argument containing spaces, wrap the command in a small script:

#!/usr/bin/env bash
# /usr/local/bin/risuko-to-nas.sh
rsync -a "$RISUKO_PATH" /Volumes/nas/incoming/

Command: /usr/local/bin/risuko-to-nas.sh
Args:    (leave empty — env vars carry the values)

Example: Conditional handling

#!/usr/bin/env bash
# /usr/local/bin/risuko-complete.sh
set -euo pipefail

case "$RISUKO_STATUS" in
  complete) /usr/local/bin/transcode.sh "$RISUKO_PATH" ;;
  error)    logger -t risuko "task $RISUKO_HASH failed: $RISUKO_PATH" ;;
  *)        ;;
esac

Command: /usr/local/bin/risuko-complete.sh
Args:    (leave empty — env vars carry the values)