Skip to content

fix(compose): honor external S3 settings - #4151

Open
ShiroKSH wants to merge 1 commit into
block:mainfrom
ShiroKSH:fix/compose-external-s3
Open

fix(compose): honor external S3 settings#4151
ShiroKSH wants to merge 1 commit into
block:mainfrom
ShiroKSH:fix/compose-external-s3

Conversation

@ShiroKSH

@ShiroKSH ShiroKSH commented Aug 1, 2026

Copy link
Copy Markdown

Problem

The Compose relay environment hardcoded its S3 endpoint and addressing style, so values set in .env were silently ignored. That sent media to the bundled MinIO service instead of the configured S3-compatible provider.

Fixes #3794.

Change

  • Preserve the bundled MinIO defaults when S3 variables are unset.
  • Pass BUZZ_S3_ENDPOINT, BUZZ_S3_REGION, and BUZZ_S3_ADDRESSING_STYLE from .env to the relay.
  • Document the external-storage path and that the base stack still starts MinIO.

Validation

  • git diff --check
  • Rendered Compose config with default values: MinIO endpoint, us-east-1, and path addressing.
  • Rendered Compose config with external overrides: endpoint, region, and virtual addressing passed through unchanged.

Signed-off-by: ShiroKSH <kushidashiro@gmail.com>
@ShiroKSH
ShiroKSH requested a review from a team as a code owner August 1, 2026 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(compose): BUZZ_S3_ENDPOINT is hardcoded, so .env cannot point media at external S3

1 participant