v0.1.1

Full Changelog: v0.1.0...v0.1.1

v0.1.0

First release.

rookery is one web UI for a fleet of WebLinked instances. Tag them into groups, fan any WebLinked command out to a group or the whole fleet over OSC, and watch each instance's real state come back over HTTP. A desk or cue stack can drive the same groups with one OSC message.

What's in it

• Groups derived from tags — an instance can be in as many as you like, and membership is resolved when a command is sent, so retagging takes effect on the next cue.
• Fan-out over OSC — navigate, reload, run a script the graphic already defines, mute, set the raster, start or stop a named output. Aimed at one instance, a group, or everything.
• A live dashboard — each instance polled over its own HTTP API: what it is showing, which outputs are running, NDI receivers attached, whether the clock is keeping up.
• Northbound OSC — /rookery/group/stage/url. The verbs are WebLinked's own, so an existing Companion button becomes a whole-group button by editing the front of the address.
• Multi-source aware — address one pipeline inside a multi-source instance, across a whole group.
• Discovery — an active subnet probe, since WebLinked does not advertise itself.

Two things to know before you rely on it

A send is not a confirmation. OSC over UDP has no acknowledgement and WebLinked replies with nothing, so "sent" means exactly the datagram left this machine. The dashboard is the confirmation. Nothing in the UI or the API claims otherwise.

WebLinked binds its HTTP server to 127.0.0.1 by default. Start each instance with --bind 0.0.0.0 or rookery cannot poll it — commands will go out fine and no state will ever come back. It is the single most likely reason a newly added instance looks broken.

Verified

Against three real WebLinked 0.7.1 instances: state polling, url (including the 3-mod-4 string length that WebLinked's own OSC decoder used to drop silently), mute, format, output, script proven to execute rather than merely arrive, group fan-out reaching exactly its members, and the full northbound chain driven by an independent OSC encoder written from the spec.

All of that was on one machine over loopback. Nothing here has been across a real show network, and discovery has never found a real instance on a real LAN. docs/verification.md is the authority and is deliberately more pessimistic than this summary.

Security

rookery has no authentication, and neither does the thing it drives — WebLinked's OSC listener accepts commands from anyone who can reach the port. Treat rookery, its northbound OSC port and every instance it manages as one trust domain on a trusted show network. Instance tokens are encrypted at rest.

Install

macOS .pkg / .dmg, Windows installer .exe, Linux .deb / .rpm, or the plain .tar.gz / .zip for all three. x86_64 and arm64 throughout.