v0.1.16

Highlights

• Raindrop Workshop can now receive traces from Docker containers and other same-host clients through the opt-in RAINDROP_WORKSHOP_ALLOWED_HOSTS setting.
• Allowed-host parsing now safely accepts hostnames, host-and-port values, and URL-shaped values while ignoring malformed entries.
• Workshop remains loopback-only by default. When allowed hosts are configured, connections are still limited to private and local-network addresses; public internet addresses remain blocked.

Using Workshop from Docker

Start Workshop on the host with an explicit bind address and allowed hostname:

RAINDROP_WORKSHOP_BIND_HOST=0.0.0.0 \
RAINDROP_WORKSHOP_ALLOWED_HOSTS=host.docker.internal \
  raindrop workshop

Then configure the container to send traces to http://host.docker.internal:5899.

Upgrade

raindrop update
raindrop workshop stop && raindrop workshop start

Restart Workshop after updating if it is already running.

v0.1.15

Add an ability to import traces from the cloud

v0.1.14

Bug fixes

v0.1.13

Add optional raindrop cloud instrumentation support

v0.1.12

release: v0.1.12

Co-authored-by: Ryan D'Onofrio <ryan@raindrop.ai>

v0.1.11

Another thanks to @haasonsaas for his contributions!

v0.1.10

Thanks to @haasonsaas

What's Changed

• Restrict HTTP-managed replay agent config by @haasonsaas
• Bind Workshop control plane to loopback by @haasonsaas
• Restrict Workshop websocket upgrades to local origins by @haasonsaas

v0.1.9

Json Tools and Windows Build

v0.1.8

release: v0.1.8

Co-authored-by: Ryan D'Onofrio <ryan@raindrop.ai>

v0.1.7

What's Changed

• Add LiveKit Agents support by @Hormold in #9