fix: support virtual-hosted S3 URLs for avatar storage (#330)

Browse Source

Avatar images failed to load with 403 on Tigris and newer AWS S3 buckets
because getAvatarUrl only constructed path-style URLs. Modern S3-compatible
providers require virtual-hosted URLs (bucket.domain/key).

Add NEXT_PUBLIC_STORAGE_DOMAIN env var to signal URL style:
- If set: virtual-hosted URL (Tigris, AWS S3)
- If not set: path-style URL (MinIO, LocalStack) - backward compatible

Add vitest and tests for getAvatarUrl behavior.

Co-authored-by: Sachin Divekar <sachin.divekar@remiges.tech>

...

This commit is contained in:

Sachin Divekar

2026-01-25 03:32:41 +05:30

committed by GitHub

parent b18ef10313

commit 6729c2e228

4 changed files with 994 additions and 17 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

927

pnpm-lock.yaml generated

File diff suppressed because it is too large Load Diff