hubfly stream
hubfly stream creates and operates Managed Streams servers: live video and audio servers that take streams in over RTMP, RTMPS, SRT, WHIP and Icecast, transcode them, restream them to other platforms and play them back over WebRTC, LL-HLS and HLS. It covers servers, inputs and stream keys, channels, destinations, mixers, playlists, schedules, recordings, playback keys, webhooks and live control, and it can publish a file or camera from your machine and open a channel in a player. hubfly live is an alias.
Basics
<server>is a stream server id or name. When two managed projects use the same name, add--project <id|name>.<input>,<channel>,<destination>and the other resources are ids (such assin_cam1abcdorsch_main0001) or names.- Every server has its own host, such as
acme-tv.live.hubfly.app. Encoders send to it and viewers play from it. - Hubfly space chooses where stream servers run, so there is no
--regionflag. You choose a speed instead: the outgoing bandwidth cap in Mbps. - Commands that print data accept
--json. Stream keys and secrets are masked unless you reveal them; new keys and secrets print once when they are created or rotated. - Every
createandupdatealso takes--file <spec.json|->with a full Dashboard API body (camelCase). Flags you pass on top change that body. - Run
hubfly stream helpfor the full usage text, andhubfly stream <resource> helpfor one resource.
terminal
Servers And Speed
hubfly stream list [--project <id|name>] [--json]
hubfly stream info <server> [--json]
hubfly stream create [<name>] [--speed <mbps>] [--processing <mbps>] [--timezone <tz>]
[--input <name>|--no-input] [--project <id|name|new>] [--project-name <name>]
[--yes] [--no-wait] [--timeout <duration>] [--json]
hubfly stream speed <server> <mbps> [--processing <mbps>] [--yes] [--no-wait] [--json]
hubfly stream delete <server> [--yes] [--wait]| Command | What it does |
|---|---|
stream list | Stream servers in your managed projects with status, monthly speed price, project and id. |
stream info | Status, host, speed, processing, WebRTC session cap, time zone and configuration state of one server, its ingest URLs, and a live summary (inputs, channels, viewers, outgoing Mbps) while something is on air. |
stream create | Quotes the speed price, asks you to confirm, creates the server and waits until it is ready. Speed defaults to 25 Mbps. The server comes with a push input named Main (--input renames it, --no-input skips it), and the command prints that input's stream key once together with the OBS settings. --project new creates a managed project for the server (--project-name names it). |
stream speed | Quotes the new speed price and changes the speed after you confirm. The change applies live: publishers and viewers stay connected. --processing also changes the reserved transcoding capacity. |
stream delete | Deletes the server after you type its name (or pass --yes). Deletion protection must be off. --wait follows the deletion until it finishes. |
Speed is billed while the server runs, and the first 25 Mbps of every hour are free, shared by all your running servers; the quote shows both the list price and the price if this is your only running server. Processing (transcoding) and bandwidth are billed by use, and ingest is free. See pricing and limits.
terminal
Lifecycle And Settings
hubfly stream start|stop <server> [--no-wait] [--json]
hubfly stream rename <server> <new-name>
hubfly stream protect <server> on|off
hubfly stream operations <server> [--limit <n>] [--json]
hubfly stream settings <server> [--timezone <tz>] [--offline-slate <graphic>|none]
[--origins <a,b>|none] [--webrtc-sessions <n>] [--json]| Command | What it does |
|---|---|
stream stop, start | A stopped server takes no publishers and serves no media, and it costs nothing. Players show it as offline and connect again when you start it. |
stream rename, protect | Change the display name (the host stays) or turn deletion protection on or off. |
stream operations | Recent operations (create, speed changes, start, stop, delete) with their status. |
stream settings | Without flags, shows the settings. --timezone is the IANA time zone used by schedules (such as Africa/Kigali). --offline-slate picks the graphic channels show while nothing is live. --origins limits which websites may embed the server's channels (none allows any). --webrtc-sessions caps concurrent WebRTC viewers; past the cap, players fall back to LL-HLS. |
terminal
Inputs And Stream Keys
hubfly stream inputs [list] <server> [--json]
hubfly stream inputs get <server> <input> [--json]
hubfly stream inputs create <server> <name> [--protocols rtmp,rtmps,srt,whip,icecast] [--backup-key]
[--pull <url>] [--pull-transport auto|tcp|udp] [--max-bitrate <kbps>]
[--allow <cidr>...] [--srt-passphrase-stdin] [--disabled] [--file <spec.json|->] [--json]
hubfly stream inputs update <server> <input> [--name <name>] [--protocols <list>] [--enable|--disable]
[--pull <url>] [--max-bitrate <kbps>] [--allow <cidr>...|--allow none]
[--srt-passphrase-stdin] [--file <spec.json|->] [--json]
hubfly stream inputs delete <server> <input> [--yes]
hubfly stream inputs keys reveal <server> <input> [--json]
hubfly stream inputs keys rotate <server> <input> [--role primary|backup] [--remove] [--yes] [--json]An input is where an encoder sends its stream. A push input has a primary stream key and an optional backup key; a pull input (--pull) fetches an rtmp, rtmps, rtsp, rtsps, srt or https HLS URL instead.
| Command or flag | Meaning |
|---|---|
inputs get | Connection details for each protocol the input accepts, with the keys masked. |
inputs create | Prints the new stream key once, with the OBS settings. --backup-key also creates a backup key for a second encoder. |
--protocols | The protocols the input accepts. Turn on whip for browser publishing and icecast for radio sources. |
--max-bitrate, --allow | Refuse publishers above a bitrate (1–80,000 kbps), or from outside the listed networks (--allow none clears the list). |
--srt-passphrase-stdin | Reads an SRT encryption passphrase (10–79 characters) from standard input. |
inputs keys reveal | Shows the primary and backup keys, the SRT passphrase or the pull URL. It needs stream admin permission. |
inputs keys rotate | Replaces the primary key (or with --role backup, the backup key, adding one if there was none) after you confirm, and prints the new key once. The encoder using the old key is disconnected. --role backup --remove deletes the backup key. |
inputs delete | Disconnects the input's publishers and invalidates its keys. It is refused while a channel, mixer or destination uses the input. |
| Protocol | Encoder URL | Where the key goes |
|---|---|---|
| RTMPS (port 443) | rtmps://acme-tv.live.hubfly.app:443/live | Stream key field |
| RTMP (port 1935) | rtmp://acme-tv.live.hubfly.app/live | Stream key field |
| SRT (UDP 9000) | srt://acme-tv.live.hubfly.app:9000?streamid=publish:<key> | streamid |
| WHIP | https://acme-tv.live.hubfly.app/whip/<input id> | Bearer token |
| Icecast (port 8000) | icecast://source:<key>@acme-tv.live.hubfly.app:8000/radio/<input id> | Password |
See OBS and encoders for encoder settings and radio for Icecast sources.
terminal
Channels And Playback
hubfly stream channels [list] <server> [--json]
hubfly stream channels get <server> <channel> [--json]
hubfly stream channels create <server> <name> --source input:<id|name>|mixer:<id|name>|playlist:<id|name>
[--backup <source>] [--latency standard|low|ultra] [--access public|token]
[--allowed-origins <a,b>|none] [--dvr <minutes>] [--max-viewers <n>]
[--no-webrtc] [--no-ll-hls] [--disabled] [--file <spec.json|->] [--json]
hubfly stream channels update <server> <channel> [same flags] [--name <name>] [--backup none]
[--webrtc[=false]] [--ll-hls[=false]] [--hls[=false]] [--enable|--disable]
hubfly stream channels delete <server> <channel> [--yes]
hubfly stream channels playback <server> <channel> [--json]
hubfly stream channels token <server> <channel> [--ttl 1h] [--sub <viewer>] [--ip <cidr>] [--json]A channel is what viewers watch. It plays an input, a mixer or a playlist, and can fall back to a backup source when its source goes silent.
| Flag or command | Meaning |
|---|---|
--source, --backup | What the channel plays, as input:, mixer: or playlist: followed by an id or name. --backup none removes the backup. |
--latency | standard, low or ultra. |
--access | public, or token to require a signed playback token. |
--allowed-origins | Websites allowed to embed this channel. |
--dvr | Minutes viewers can rewind (0–360). Clips are cut from the DVR. |
--max-viewers | Cap on concurrent viewers. |
--no-webrtc, --no-ll-hls | Turn off WebRTC (WHEP) or low-latency HLS output. On update use --webrtc=false, --ll-hls=false or --hls=false, and =true to turn them back on. |
channels playback | The channel's HLS, WebRTC (WHEP), embed, thumbnail and status URLs, any pull and audio outputs, and ready-to-paste embed code. |
channels token | A test playback token for a token channel, signed by the server's newest active playback key. --ttl is 60 seconds to 24 hours (1 hour by default); --sub labels the viewer and --ip binds the token to a network. The token goes to standard output and its expiry to standard error. |
| Output | URL |
|---|---|
| HLS and LL-HLS | https://acme-tv.live.hubfly.app/hls/<channel>/index.m3u8 |
| WebRTC (WHEP) | https://acme-tv.live.hubfly.app/whep/<channel> |
| Embed page | https://acme-tv.live.hubfly.app/embed/<channel> |
| Status | https://acme-tv.live.hubfly.app/status/<channel>.json |
| Thumbnail | https://acme-tv.live.hubfly.app/thumb/<channel>.jpg |
Token channels take the token as ?token= on these URLs. To build a player into your site, use @hubfly/streams.
terminal
Destinations
hubfly stream destinations [list] <server> [--json]
hubfly stream destinations get <server> <destination> [--json]
hubfly stream destinations create <server> <name> --platform youtube|twitch|facebook|kick|x|linkedin|custom
--source channel:<id|name>|input:<id|name> --stream-key-stdin [--url <url>]
[--protocol rtmp|rtmps|srt] [--rendition <name>] [--auto-start[=false]]
[--srt-passphrase-stdin] [--disabled] [--file <spec.json|->] [--json]
hubfly stream destinations update <server> <destination> [--name <name>] [--source <source>] [--url <url>]
[--protocol rtmp|rtmps|srt] [--rendition <name>] [--auto-start[=false]]
[--stream-key-stdin] [--enable|--disable] [--file <spec.json|->] [--json]
hubfly stream destinations start|stop <server> <destination> [--json]
hubfly stream destinations delete <server> <destination> [--yes]- A destination restreams a channel or an input to another platform. Platform presets fill in the ingest URL;
customandlinkedinneed--url. You cannot change the platform of an existing destination. - The platform's stream key is read from standard input with
--stream-key-stdin; there is no flag that takes it as an argument, so it never appears in your shell history or process list. Hubfly space shows only a hint of it afterwards. --auto-startstarts the push whenever the source goes live.destinations startandstopturn it on and off by hand.--renditionsends one rendition of a transcoded channel instead of the source quality.
See restreaming.
terminal
Mixers, Playlists And Schedules
hubfly stream mixers [list|get|delete] <server> ...
hubfly stream mixers create <server> <name> [--preset vertical|1080p30|1080p60|720p30] [--disabled] [--file <spec.json|->]
hubfly stream mixers update <server> <mixer> [--name <name>] [--enable|--disable] [--default-scene <scene>]
[--transition cut|fade:<duration>] [--file <spec.json|->]
hubfly stream scene list <server> <mixer> [--json]
hubfly stream scene switch <server> <mixer> <scene> [--fade <duration>|--cut] [--json]
hubfly stream playlists [list|get|delete] <server> ...
hubfly stream playlists create <server> <name> --item <url|asset:<link>:<asset id>|object:<link>:<key>>...
[--loop] [--shuffle] [--encoding auto|reencode] [--file <spec.json|->]
hubfly stream playlists update <server> <playlist> [--name <name>] [--item …]... [--loop[=false]]
[--shuffle[=false]] [--encoding auto|reencode] [--file <spec.json|->]
hubfly stream schedules [list|get|delete] <server> ...
hubfly stream schedules create <server> <name> --start <local time> --duration <minutes> [--rrule <rule>]
[--timezone <tz>] [--on-start '<op json>']... [--on-end '<op json>']...
[--disabled] [--file <spec.json|->]
hubfly stream schedules update <server> <schedule> [same flags] [--rrule none] [--enable|--disable]
hubfly stream schedules preview <server> --start <time> --duration <minutes> [--rrule <rule>] [--timezone <tz>] [--json]
hubfly stream schedules runs <server> <schedule> [--limit <n>] [--before <cursor>] [--json]| Resource | What it is |
|---|---|
| Mixer | A canvas that composes inputs, graphics and text into scenes, like a studio switcher. Flags cover the canvas preset, the default scene and the transition (cut, or fade:500ms up to 10 seconds). Scenes and their layers are defined in the --file body. Mixers re-encode, so they use processing. |
| Scene switch | scene switch changes a mixer's live scene, by scene id or name, with a fade (500 ms when you give no duration) or a hard cut. scene list shows the scenes and which is the default. |
| Playlist | Files played as a live source: http(s) URLs (HLS when the URL contains .m3u8), assets of a storage link (asset:<link>:<asset id>) or objects in its bucket (object:<link>:<key>). Repeat --item to add several. --encoding reencode forces transcoding of mixed files. |
| Schedule | Runs control operations at a time: --on-start operations at --start (a local time such as 2026-11-02T18:00 in the schedule's time zone, the server's by default) and --on-end operations after --duration minutes (up to 7 days). --rrule repeats it with an RFC 5545 rule such as FREQ=WEEKLY;BYDAY=MO. schedules get lists the next starts, preview computes them without saving, and runs shows past runs. |
A --file body uses the Dashboard API field names in camelCase, the same as the API reference. Use - to read it from standard input, and get --json to start from an existing resource. See studio and graphics and playlists and schedules.
{
"name": "Show",
"preset": "1080p30",
"sources": [
{ "id": "cam", "type": "input", "ref": "sin_cam1abcd" },
{ "id": "logo", "type": "image", "ref": "sgr_logo0001" }
],
"scenes": [
{
"id": "main",
"name": "Main",
"layers": [
{ "source": "cam", "x": 0, "y": 0, "w": 1920, "h": 1080,
"crop": { "l": 0, "t": 0, "r": 0, "b": 0 }, "z": 0, "opacity": 1, "visible": true },
{ "source": "logo", "x": 40, "y": 40, "w": 160, "h": 160,
"crop": { "l": 0, "t": 0, "r": 0, "b": 0 }, "z": 1, "opacity": 0.9, "visible": true }
],
"audio": [{ "source": "cam", "gainDb": 0, "muted": false }]
}
],
"defaultScene": "main"
}terminal
Recordings And Clips
hubfly stream recordings [list] <server> [--kind recording|clip] [--channel <channel>] [--limit <n>] [--cursor <c>] [--json]
hubfly stream recordings delete <server> <recording> [--delete-object] [--yes]
hubfly stream clips [list] <server> [--channel <channel>] [--json]
hubfly stream clips create <server> --channel <channel> --from <time|-90s> --to <time|-0s> --name <name>
[--storage-link <link>] [--json]
hubfly stream clips delete <server> <clip> [--delete-object] [--yes]- Recordings are written to an Object Storage bucket through a storage link. Start and stop them with
stream control --record-startand--record-stop, or from a schedule. clips createcuts a clip from the channel's DVR, so the channel needs--dvrminutes.--fromand--toare RFC 3339 times or offsets from now such as-90s.deleteremoves the entry;--delete-objectalso deletes the file from the bucket.
See recording and clips.
terminal
Playback Keys And Bindings
hubfly stream playback-keys [list] <server> [--json]
hubfly stream playback-keys create <server> <name> [--json] (the secret prints once)
hubfly stream playback-keys rotate <server> <key> [--yes] [--json] (new secret once; the old key retires in 24 h)
hubfly stream playback-keys delete <server> <key> [--yes]
hubfly stream bindings [list] <server> [--json]
hubfly stream bindings create <server> --to <project> [--playback-key <key>] [--channel <channel>]
[--client-prefix none|NEXT_PUBLIC_|VITE_|PUBLIC_] [--json]
hubfly stream bindings delete <server> <binding> [--remove-variables] [--yes]- Channels with
--access tokenplay only with a token signed by one of the server's playback keys. Your backend signs a short-lived token per viewer withsignPlaybackToken, after checking its own session. playback-keys createprints the key's secret once.rotateprints a new secret once and keeps the old key working for 24 hours so you can redeploy.deleteinvalidates every token signed with the key at once.bindings createwritesHUBFLY_STREAM_URL,HUBFLY_STREAM_PLAYBACK_KEY_IDandHUBFLY_STREAM_PLAYBACK_KEY_SECRET(a secret variable) into a Cell project;--client-prefixadds browser copies of the public values, never of the secret. Redeploy the project to load them.bindings delete --remove-variablesalso removes the variables.
See playback security.
terminal
Webhooks
hubfly stream webhooks [list] <server> [--json]
hubfly stream webhooks create <server> --url <https-url> [--events channel.live,input.connected] [--disabled] [--json]
hubfly stream webhooks update <server> <webhook> [--url <url>] [--events <a,b>|all] [--enable|--disable] [--json]
hubfly stream webhooks test <server> <webhook> [--json]
hubfly stream webhooks deliveries <server> <webhook> [--limit <n>] [--after <cursor>] [--json]
hubfly stream webhooks delete <server> <webhook> [--yes]- Webhook URLs must use
https://. Without--eventsa webhook receives every event;--events allresets a filter. - Events:
input.connected,input.disconnected,input.failover,channel.live,channel.offline,destination.connected,destination.failed,destination.stopped,recording.started,recording.completed,recording.failed,clip.completed,clip.failed,schedule.fired,schedule.missed,schedule.failed,processing.rejected,speed.throttled,billing.blocked,billing.unblockedandplaylist.item. createprints the webhook'swhsec_signing secret once. Verify theHubfly space-Signatureheader of every delivery with it (verifyWebhook).testsends a test delivery and prints the response;deliverieslists recent attempts and their status.
See webhooks.
terminal
Graphics, Storage And Domains
hubfly stream graphics [list|get|delete] <server> ...
hubfly stream graphics upload <server> <file> [--name <name>] [--kind image|svg|html|font] [--content-type <type>] [--json]
hubfly stream graphics update <server> <graphic> [--name <name>] [--var <key>=<value>]... [--json]
hubfly stream storage-links [list] <server> [--json]
hubfly stream storage-links create <server> --storage-project <id|name> --bucket <bucket> [--mode read|write|read_write] [--json]
hubfly stream storage-links assets <server> <link> [--search <text>] [--hls-ready] [--json]
hubfly stream storage-links delete <server> <link> [--yes]
hubfly stream domains [list] <server> [--json]
hubfly stream domains create <server> <hostname> [--purpose both|playback|ingest] [--json]
hubfly stream domains verify <server> <domain> [--json]
hubfly stream domains delete <server> <domain> [--yes]| Command | What it does |
|---|---|
graphics upload | Uploads an image (PNG, JPEG, GIF, WebP), SVG, HTML template or font of up to 5 MiB for mixers and slates. The kind and content type come from the file extension unless you set them; the name defaults to the file name. |
graphics update --var | Sets template variables of an HTML or SVG graphic, such as a lower-third name. --var key= removes one. To change them live during a show, use the graphics.set control operation. |
storage-links create | Links a bucket of one of your Object Storage projects for recordings, clips, playlists and graphics (read_write by default). assets lists the files in it; --hls-ready shows only assets already encoded for streaming. Deleting a link revokes its access key, and recordings, playlists and graphics that use it stop working. |
domains create | Adds a custom hostname for playback, ingest or both and prints the CNAME record to add (pointing at the server's *.live.hubfly.app host). Run domains verify once the record is in place. |
See custom domains.
terminal
Live Control
hubfly stream control <server> [--go-live <channel>]... [--stop <channel>]...
[--destination-start <destination>]... [--destination-stop <destination>]...
[--record-start <channel>]... [--record-stop <channel>]...
[--slate <channel>=on|off]... [--disconnect <input>[:primary|backup]]...
[--op '<json>']... [--json]stream control sends one or more operations to the server in a single request and prints one line per operation, ok or failed with the reason. The command fails when any operation fails. Every shorthand flag can be repeated or given a comma-separated list, and takes ids or names.
| Flag | Operation |
|---|---|
--go-live, --stop | channel.start, channel.stop: put a channel on air, or take it off air (viewers see the offline slate). |
--destination-start, --destination-stop | destination.start, destination.stop: start or stop a restream. |
--record-start, --record-stop | recording.start, recording.stop: record a channel to its storage link. |
--slate <channel>=on|off | channel.slate: cut a channel to its slate and back. |
--disconnect <input>[:role] | input.disconnect: disconnect an input's publisher, or only its primary or backup. |
--op '<json>' | Any operation as a JSON object, or an array of them, with resource ids and camelCase fields: mixer.scene, mixer.layer, mixer.audio, mixer.text, graphics.set, channel.source, clip.create, playlist.play, playlist.next and the operations above. |
terminal
Live State, Usage And Events
hubfly stream live <server> [--json]
hubfly stream usage <server> [--month YYYY-MM] [--json]
hubfly stream events <server> [--after <cursor>] [--limit <n>] [--json]
hubfly stream stats <server> [--from <time>] [--to <time>] [--channel <channel>] [--json]| Command | What it does |
|---|---|
stream live | The state of the server and of every input, channel, destination and mixer right now: who is publishing, what each channel plays, viewers, outgoing Mbps against the speed, and whether the server is throttled at its speed cap or paused by billing. |
stream usage | Speed and processing Mbps-hours, bandwidth in GB, the free allowance used, the cost so far and an estimate for the month (the current month by default). |
stream events | Server events, oldest first, 50 at a time by default. When there are more, it prints the --after cursor for the next page. Events are kept for 7 days. |
stream stats | Viewers, viewer minutes and egress per minute, for one channel or all, between two RFC 3339 times. |
terminal
Tail The Studio Socket
hubfly stream tail <server> [--meters] [--watch in:<input>,ch:<channel>,mx:<mixer>] [--json]stream tailconnects to the server's studio socket, the live feed the Dashboard studio uses, and prints events as they happen and every change of state: the server, and each input, channel, destination and mixer. Press Ctrl-C to stop. It reconnects on its own with a fresh token.--metersadds audio levels (RMS and peak in dBFS, at most once per second per source) for every input and channel, up to 16 sources.--watchchooses the sources instead:in:inputs,ch:channels andmx:mixers, by id or name.- With
--jsonit prints one JSON object per line. Secrets are masked in every frame.
terminal
Push From Your Machine
hubfly stream push <server> <file|device[:<spec>]> [--input <input>] [--protocol srt|rtmps] [--loop]
[--key-stdin] [--role primary|backup] [--bitrate <kbps>] [--ffmpeg <path>] [--dry-run]stream push publishes a video file or a capture device to an input with your local ffmpeg, which is handy to test a channel without an encoder. ffmpeg only encodes and writes the stream to its standard output; the CLI carries those bytes to the server itself over SRT (default) or RTMPS. The stream key therefore never appears in ffmpeg's arguments, environment or logs, nor in any process listing.
| Flag | Meaning |
|---|---|
<file|device> | A file path or URL, or device for the default camera (/dev/video0 on Linux, AVFoundation 0:0 on macOS). device:<spec> picks another one; Windows needs a DirectShow name such as device:video="Integrated Camera":audio="Microphone". A silent audio track is added when the device has no audio. |
--input | The input to publish to. You can leave it out when the server has one push input. |
--protocol | srt (default) or rtmps. The input must accept it. |
--loop | Repeat a file until you press Ctrl-C. |
--key-stdin | Read the stream key (and, for an SRT input that has one, the passphrase) from standard input. Without it, the CLI reveals the input's key with your account, which needs stream admin permission. |
--role | Publish with the primary (default) or backup key. |
--bitrate | Video bitrate, 300–80,000 kbps (4,500 by default). Audio is AAC 160 kbps. |
--ffmpeg, --dry-run | Use another ffmpeg binary, or print the ffmpeg command and where the stream would go without sending anything. |
If ffmpeg is missing, the command explains how to install it on your system (for example brew install ffmpeg or winget install Gyan.FFmpeg).
terminal
Play A Channel
hubfly stream play <server> <channel> [--url-only] [--ttl <duration>] [--player mpv|ffplay] [--json]stream playopens the channel's HLS output inmpv, orffplaywhen mpv is not installed (--playerchooses one). Low-latency HLS can take a few seconds to start.- For a token channel it adds a test token to the URL, valid for
--ttl(60 seconds to 24 hours, 1 hour by default). --url-onlyprints the (signed) URL instead, to open in any HLS player such as Safari or VLC;--jsonalso includes when the token expires.
terminal
Scripting And Secrets
- JSON output. With
--json, standard output carries only JSON; quotes, prompts and progress go to standard error. - Confirmations. Creating a server, changing its speed, deleting, and rotating stream or playback keys ask first. Without a terminal they stop and ask you to re-run with
--yes; pass it once you have reviewed the change. - Secrets. Stream keys, playback key secrets and webhook secrets print once when they are created or rotated; afterwards only
inputs keys revealshows stream keys again. Platform stream keys (--stream-key-stdin), SRT passphrases and the key forpush --key-stdinare read from standard input and never taken as arguments. Other output, includingeventsandtail, masks secrets. - Waiting. Creating, changing the speed, starting and stopping show progress and wait;
--no-waitreturns as soon as Hubfly space has accepted the request. Follow it later withhubfly stream operations. - Exit codes. Non-zero on failure, with distinct codes for usage errors, authentication, conflicts and timeouts. See exit codes.
Keep stream keys out of code and logs
hubfly stream inputs keys rotate if it leaks. Viewers never need it: they need only the playback URLs, plus a token for token channels.From code
client.managed.streams in the Hubfly space SDK; for players, publishing and playback tokens, use @hubfly/streams. Start with the get started guide.