Issue Station
Sign In
Tools hereToolbox

dify - ✅(Solved) Fix [Refactor/Chore] Restore missing S3 env example variable [2 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#34823•Fetched 2026-04-10 03:45:57
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
2
Author
laipz8200laipz8200
Participants
laipz8200laipz8200
Assignees
laipz8200laipz8200
Timeline (top)
assigned ×1closed ×1cross-referenced ×1

Restore the missing S3_ADDRESS_STYLE environment variable in the example env files and regenerate Docker Compose output accordingly.

Affected files:

  • api/.env.example
  • docker/.env.example
  • docker/docker-compose.yaml

The backend already supports S3_ADDRESS_STYLE with auto, virtual, and path, but the example files no longer expose it. As a result, the generated Docker Compose env block also drops it.

Root Cause

Restore the missing S3_ADDRESS_STYLE environment variable in the example env files and regenerate Docker Compose output accordingly.

Affected files:

  • api/.env.example
  • docker/.env.example
  • docker/docker-compose.yaml

The backend already supports S3_ADDRESS_STYLE with auto, virtual, and path, but the example files no longer expose it. As a result, the generated Docker Compose env block also drops it.

Fix Action

Fixed

PR fix notes

PR #34826: fix(docker): restore S3_ADDRESS_STYLE env examples

Description (problem / solution / changelog)

Summary

Fixes #34823

This PR restores the missing S3_ADDRESS_STYLE environment variable in the example env files and regenerates docker/docker-compose.yaml so the shared env block includes it again.

The gap was noticed while following up on langgenius/dify-docs#734.

Screenshots

BeforeAfter
N/AN/A

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran make lint and make type-check (backend) and cd web && pnpm exec vp staged (frontend) to appease the lint gods

Changed files

  • api/.env.example (modified, +1/-0)
  • docker/.env.example (modified, +1/-0)
  • docker/docker-compose.yaml (modified, +1/-0)
RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Description

Restore the missing S3_ADDRESS_STYLE environment variable in the example env files and regenerate Docker Compose output accordingly.

Affected files:

  • api/.env.example
  • docker/.env.example
  • docker/docker-compose.yaml

The backend already supports S3_ADDRESS_STYLE with auto, virtual, and path, but the example files no longer expose it. As a result, the generated Docker Compose env block also drops it.

Motivation

We received a documentation PR in langgenius/dify-docs#734, and during follow-up we realized this environment variable had been lost from the example files in this repository.

That leaves the docs, backend capability, and example configuration out of sync. Restoring it will make the examples match the supported runtime configuration again.

Additional Context

Reference document PR: langgenius/dify-docs#734

extent analysis

TL;DR

Restore the S3_ADDRESS_STYLE environment variable in the example env files and update the Docker Compose output to reflect the change.

Guidance

  • Add the S3_ADDRESS_STYLE variable back to the api/.env.example and docker/.env.example files with its supported values (auto, virtual, and path) to ensure consistency with the backend capabilities.
  • Regenerate the Docker Compose output to include the S3_ADDRESS_STYLE environment variable in the env block.
  • Verify that the updated example files and Docker Compose output are correctly synced with the documentation and backend support.
  • Review the documentation PR langgenius/dify-docs#734 to ensure it aligns with the restored environment variable.

Example

# api/.env.example
S3_ADDRESS_STYLE=auto

# docker/.env.example
S3_ADDRESS_STYLE=virtual

# docker/docker-compose.yaml
environment:
  - S3_ADDRESS_STYLE=${S3_ADDRESS_STYLE}

Notes

The restoration of the S3_ADDRESS_STYLE environment variable should be done carefully to avoid introducing inconsistencies with the existing documentation and backend capabilities.

Recommendation

Apply workaround: Restore the S3_ADDRESS_STYLE environment variable in the example files and update the Docker Compose output to ensure consistency with the backend support and documentation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#environment variable#search optimization#API routing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING