Originally created by @anyidea on GitHub (Mar 31, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
Currently, the application only supports one addressing style for AWS S3 connections. However, different S3-compatible services and environments may require different addressing styles:
Implement a configuration option that allows users to choose between Virtual Host Style and Path Style addressing via an environment variable called S3_ADDRESSING_STYLE(default to: path).
Users should be able to set:
S3_ADDRESSING_STYLE=virtual for Virtual Host Style
S3_ADDRESSING_STYLE=path for Path Style
Alternatives Considered
No response
Additional Context
Some S3-compatible services like MinIO may have specific requirements for the addressing style. Additionally, AWS has been encouraging the use of virtual-hosted style, but path style is still necessary in some scenarios.
Originally created by @anyidea on GitHub (Mar 31, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Currently, the application only supports one addressing style for AWS S3 connections. However, different S3-compatible services and environments may require different addressing styles:
1. Virtual Host Style: https://bucket-name.s3.amazonaws.com/key-name
2. Path Style: https://s3.amazonaws.com/bucket-name/key-name
This limitation prevents users who need to work with services that only support one specific addressing style.
Reference: https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html
### Desired Solution you'd like
Implement a configuration option that allows users to choose between Virtual Host Style and Path Style addressing via an environment variable called S3_ADDRESSING_STYLE(default to: `path`).
Users should be able to set:
S3_ADDRESSING_STYLE=virtual for Virtual Host Style
S3_ADDRESSING_STYLE=path for Path Style
### Alternatives Considered
_No response_
### Additional Context
Some S3-compatible services like MinIO may have specific requirements for the addressing style. Additionally, AWS has been encouraging the use of virtual-hosted style, but path style is still necessary in some scenarios.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @anyidea on GitHub (Mar 31, 2025).
Check Existing Issues
Problem Description
Currently, the application only supports one addressing style for AWS S3 connections. However, different S3-compatible services and environments may require different addressing styles:
This limitation prevents users who need to work with services that only support one specific addressing style.
Reference: https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html
Desired Solution you'd like
Implement a configuration option that allows users to choose between Virtual Host Style and Path Style addressing via an environment variable called S3_ADDRESSING_STYLE(default to:
path).Users should be able to set:
S3_ADDRESSING_STYLE=virtual for Virtual Host Style
S3_ADDRESSING_STYLE=path for Path Style
Alternatives Considered
No response
Additional Context
Some S3-compatible services like MinIO may have specific requirements for the addressing style. Additionally, AWS has been encouraging the use of virtual-hosted style, but path style is still necessary in some scenarios.
@tjbck commented on GitHub (Mar 31, 2025):
PR Welcome.