buzz-media: hardcoded path-style S3 addressing rules out virtual-hosted-style providers (e.g. Railway Buckets)

Open Beginner friendly
#3,273 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
rust
Domain
cloud

Research direction

Start in crates/buzz-media/src/storage.rs by tracing MediaConfig into Storage::new and inspect CONTRIBUTING for environment-variable documentation conventions. Verify that the new BUZZ_S3_FORCE_PATH_STYLE setting preserves path-style behavior by default and permits virtual-hosted-style addressing when false, then run the relevant Rust tests or checks available in the repository.

Written by the indexing model from the issue text.

Description

Problem

buzz-media hardcodes path-style S3 addressing. In crates/buzz-media/src/storage.rs the bucket client is always built with .with_path_style(), and there is no configuration to turn it off.

This rules out S3-compatible providers that only support virtual-hosted-style URLs. The concrete case I hit: Railway Buckets (their managed object storage) is virtual-hosted-style only, so a Railway self-host cannot use the platform's native storage and must run a MinIO service instead.

Proposal

Add a BUZZ_S3_FORCE_PATH_STYLE env var (default true, preserving current behavior for MinIO and existing deployments). When set to false, skip .with_path_style() so the client uses virtual-hosted-style addressing.

Small change: one field on MediaConfig, one conditional in Storage::new, docs for the new variable per CONTRIBUTING. Happy to PR it if this direction is acceptable.

Dupes checked

No existing issue or PR covers addressing style. Closest related S3-compat work: #2618 (RustFS as default backend), #2470 (GCS interop), #3002 (Ceph RGW ETags), which suggests the S3 compatibility matrix is an active concern.

Dominant language
Rust
Stars
33.7k
Forks
4.4k
Avg merge
1d 21h
Merged PRs (30d)
239

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from block/buzz

All issues in block/buzz

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.