Process video in any S3-compatible bucket
Give Rendobar an endpoint, a region and a key pair, and any job reads from and writes to MinIO, Wasabi, Backblaze B2 or Hetzner over the S3 API. The endpoint must be public https.
Overview
Jobs read objects as storage:// paths and deliver outputs back over the S3 API. The dashboard asks for the endpoint, region, bucket and a key pair, then tests them on one object before saving. The S3-compatible docs cover path-style URLs and connecting from the SDK.
Questions
Which S3-compatible providers work with Rendobar?
Any service that implements the S3 API on an https endpoint with a public host, such as MinIO, Wasabi, Backblaze B2 and Hetzner Object Storage. A server reachable only on a private network can't be connected.
When should I turn on path-style URLs?
When your provider addresses buckets as endpoint/bucket/key instead of bucket.endpoint/key. If the access checks fail with a signature or bucket error and the keys are correct, try the other setting.
What permissions does the S3-compatible key need?
Read and write on objects in the bucket. Delete isn't needed, and without it the empty test object stays at .rendobar/probe-<uuid> for you to remove. List only matters for browsing the bucket from the dashboard.
Why is Name conflicts fixed to Replace on my bucket?
When you connect, Rendobar checks whether the endpoint refuses to overwrite an existing object. If it doesn't, Keep both can't work, so the setting is fixed to Replace. Add {job_id} to the output path to keep every output.
Related
- Amazon S3 Read inputs from your S3 bucket and write every output back to it.
- Cloudflare R2 Keep your media in R2 and process it without moving it first.
- Supabase Storage Process files in your Supabase bucket and land the results next to them.
