Skip to main content

Reload

hypermass reload applies changes in hypermass-config.yaml to a running hypermass sync, without restarting it. hypermass subscribe and hypermass publish run it for you.

hypermass reload
  • Added streams start.
  • Removed streams stop.
  • Changed streams restart with their new settings.
  • Unchanged streams carry on undisturbed.

The output lists what changed:

✅ Reloaded: 1 added, 1 changed, 0 removed, 3 unchanged
  + _254gGE43g  subscription started
  ~ _XXYYZZ  publication restarted

Waiting for transfers​

A stream that stops waits for the file it is transferring to finish, so hypermass reload can take a moment. Add --no-wait to return straight away, then follow progress with hypermass status.

When something can't start​

A stream that can't start - for example, one pointed at a folder belonging to another stream - is listed as failed, and hypermass status shows why. The rest carry on. Fix the entry and run hypermass reload again.

Invalid YAML is rejected as a whole, leaving everything running as it was.

Changing your access key​

hypermass reload reads the configuration file only. After hypermass login, restart hypermass sync to use the new key.