Working Directory Management

Every node has a working directory — where it stores cached media, show files, and internal state. By default this is a .wo folder next to the WATCHOUT installation. Change it on any node to store data on a different drive, such as a faster SSD or a larger volume.

What the working directory contains

  • Cached assets — local copies of media downloaded from the Asset Manager for playback.
  • Show data — shows loaded or uploaded to the node.
  • Runtime files — internal state used by WATCHOUT services.

This data lives at the working directory's path. If the directory changes, the node loses access to data at the old path.

Changing the working directory

  1. Open the Nodes window and select the node.
  2. In Node Properties, under the System actions, click Change Working Directory. The dialog opens.
  3. Enter or browse to the new path.
  4. Check I understand, then click OK.

The dialog warns that:

  • The path must be an existing directory on the node. WATCHOUT checks it exists before accepting.
  • All cached assets at the old location stay on disk but are no longer used.
  • Some error messages appear briefly as the connection to the old Asset Manager storage drops.

Changing the working directory means all cached assets must be re-transferred from the Asset Manager. This takes time with a large library. Do it in a maintenance window, not during a show.

Resetting to the default

To return a node to the default .wo location, click Reset to Default inside the Change Working Directory dialog. The button is enabled only after you check I understand. The same re-transfer applies.

Use cases

  • A faster or larger drive — point the working directory to a dedicated SSD or a larger volume.
  • Separate OS and show data — keep Windows and WATCHOUT on one drive and show data on another for easier backup.
  • Standard paths across a fleet — use the same path on every Runner for consistency.

If the directory is unavailable

At startup, if the configured directory is missing and cannot be created, the node falls back to the default .wo location. If that also fails, the node management service logs an error and stops. This check runs at startup, not while the node is running. For diagnosing storage problems, see Network Issues.

Previous Next