Skip to content

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 24 Oct 15:31
· 504 commits to main since this release
99efe1b

Outpace 0.8.0

Since v0.7.0, Outpace adds managed HTTP broadcast sources, immutable broadcast startup profiles, and a default per-stream inbound admission cap.

Broadcast origination

  • Pull HTTP(S) MPEG-TS through PUT/GET/DELETE /broadcast/{name}/source or OUTPACE_BROADCAST_SOURCES. A managed worker reconnects with bounded backoff and discards incomplete reconnect tails. Startup declarations reattach after restart; API-only attachments are process-local. Raw PUT, RTMP and pull share exclusive producer ownership (#267).
  • Signing indexes are reserved in persistent 128-piece blocks before publication. Restart skips unused reservations; malformed identity state fails closed. Shutdown and deletion retain fences for unfinished persistence work. One daemon must exclusively own its data directory. Windows protects process-crash/ordinary restart while OS/filesystem state survives; system crash or power loss can roll back reservations, lose identities or resurrect deleted records. Linux/macOS guarantees also depend on filesystem/storage sync semantics. Older binaries ignore reservations: before rollback, stop origination and deliberately remove the old identity, then originate a fresh identity. Restoring old signing state can reuse indexes.
  • OUTPACE_BROADCAST_OPTIONS supplies immutable named profiles for title, bitrate in bytes/second, piece length, quality and ordered categories across PUT, RTMP, pull and CLI origination. Stored transport bytes and identity remain authoritative; conflicting explicit options fail. Resume announcements now use stored trackers, so changing OUTPACE_TRACKERS affects fresh identities only. Store budgets must fit a complete piece, including declared profiles and valid stored broadcasts (#273).

Deployment impact

  • New default: OUTPACE_MAX_INBOUND_PER_STREAM=16 caps combined media/metadata admissions per canonical stream. The 17th admission closes before a handshake reply. Set 0 to restore global-only admission, then restart/recreate; Compose needs an explicit service environment override. The global retained-connection default remains 64. This bounds occupancy, not bandwidth, equal service or session lifetime (#268).
  • Both broadcast JSON settings default to {}. Profiles have no hot reload and do not create broadcasts by themselves; invalid/conflicting configuration can fail startup. Fresh unprofiled defaults remain title from path, bitrate 8375 bytes/s, piece length 65536, quality auto, categories ["other"].
  • Pull access to non-global sources stays off unless the operator sets exactly OUTPACE_ALLOW_NON_GLOBAL_BROADCAST_SOURCE=1. Fetches validate/pin DNS and verify TLS; redirects and proxies are disabled. Transport URL fetching now also ignores proxy environment settings. Source routes use the existing native listener policy; protect mutation access with a firewall/authenticating proxy. No new authentication framework or listener exposure is added. Compose examples forward source declarations and the source address opt-in; profiles require explicit forwarding.

Evidence and remaining scope

#205 records signed playback by actual official-engine and Outpace consumers in isolated synthetic Linux windows, with separate restart, load and RTMP evidence. Both consumers had corrupt-frame episodes; strict raw-byte continuity and an RTMP status predicate remained unmet. This establishes bounded local origination/playback, without establishing error-free playback, WAN/NAT reachability, public deployment, whole-stream byte identity or long-term reliability.

Optional discovery/metadata wire fields (#269), autonomous support nodes (#270), private peer policy (#271) and HLS transport/support parity (#272) remain follow-ups. Native MPEG-TS-to-HLS packaging does not establish HLS origination parity.

All eight local workspace packages move to 0.8.0. Release preparation changes version metadata only; it does not upgrade dependencies or change the existing seven-archive/checksum and multi-platform container workflows. See the native API and deployment guidance for configuration and persistence limits.