Skip to content

Neat Insight v0.0.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 19 Jun 19:04
v0.0.3
41c486e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Neat Insight v0.0.3

This patch improves Insight usability inside the Neat Development Environment, especially when sima-cli maps services to non-default host ports.

What changed

Insight now builds DevKit WebSSH launch URLs from the SDK port map when one is available. The WebSSH service can still listen on its internal container port, but browser-facing links now use the exposed host port from neat-port-map.json. This matches the existing Video Viewer behavior and keeps WebSSH links working when default ports are already occupied.

The Insight documentation and agent guidance were also expanded around SDK port mapping, media setup, and RTSP/WebRTC workflows. The docs now make the boundary between container ports and host-exposed SDK ports more explicit, with guidance for insight-admin status, neat --json, DevKit workflows, media import, and common video asset locations.

Why this matters

When Insight runs inside the Neat Development Environment, the ports users click in a browser are not always the same as the ports services use inside the container. If Insight assumes the internal WebSSH port, browser links can fail with connection errors even though the service is running correctly.

This release makes WebSSH launch behavior consistent with the rest of Insight's browser-facing URLs. It also gives users and coding agents clearer instructions for choosing the right RTSP, WebRTC, UDP, and WebSSH endpoints in SDK-local, DevKit, and external-application setups.

User benefit

  • WebSSH links work when sima-cli allocates a non-default host port.
  • Insight more accurately reflects the active SDK port map.
  • Fewer confusing connection failures caused by mixing container ports and host ports.
  • Clearer setup guidance for media files, DevKit streaming, and RTSP/WebRTC paths.
  • Better agent guidance for automating Insight workflows from the SDK environment.

Compatibility

This is intended as a patch-level update for Insight. Existing Insight workflows and APIs remain compatible.

Users running Insight through the Neat Development Environment should see improved WebSSH behavior without changing their commands.

Validation

The WebSSH port-map fix was covered by focused URL generation tests, including mapped host-port and IPv6 formatting cases. The documentation updates were reviewed for Markdown structure, link coverage, and SDK workflow consistency.

Included changes

  • Expand Insight docs for SDK port mapping and media setup in #33
  • Promote documentation and SDK workflow updates through main in #34
  • Honor mapped WebSSH host ports in #36
  • Promote WebSSH port-map handling through main in #39

Full Changelog: v0.0.2...v0.0.3

Assets 2
Loading