Video & playback
Hubfly space Storage can turn a source video in a bucket into HLS renditions. Encoding runs as a background job, so receiving a job ID means the request was queued, not that playback is ready.
Upload a source
- Create a bucket or choose an existing one.
- Request a media upload session with
bucket,objectKey, and the videocontentType. - PUT the complete source file to
upload_urlbeforeexpires_at. Keep the returnedobject_key.
The session upload path requires a known Content-Length and rejects sources over 20 GB. Do not send source bytes through the Dashboard JSON API. For a trusted server, the S3 API can also upload the object directly.
Encode HLS
Call media encode with the bucket, source key, and a maximum height of 360, 480, 720, or 1080. The response contains a job ID and state. Poll the media list for progress and errors. You can also register the source as a managed asset, then request selected renditions through the asset encoding endpoint.
From a terminal, upload the source and start encoding with the CLI; --wait follows the job until it is ready or fails:
hubfly storage put ./intro.mp4 project-assets/videos/
hubfly storage encode project-assets/videos/intro.mp4 --max-height 720 --wait
hubfly storage media # jobs, states and errorsEncoding is asynchronous
Play the video
Call create playback with the ready job ID. The response contains manifest_url, player_url, and expires_at. Give the player URL to the intended viewer. The signed URL expires; request a fresh one when needed. HLS-compatible players use the manifest and segment URLs returned by the service.
Manage renditions
If a rendition fails or should be replaced, inspect the media job and source object, then request re-encoding for that rendition. Delete a rendition only after removing live player references to it. Removing an asset or its source may also remove or invalidate generated media.
See the media API reference for request fields, job responses, rendition deletion, and re-encoding.