hairyEagle a9ee3d1ea6 fix(selfhost): configure bucket CORS in s3-init so browser uploads work (#3934) ...

Browser uploads (Dev Center deploy, puter.fs.upload) PUT file bytes
directly to presigned URLs on the public S3 endpoint. That cross-origin
PUT is preflighted, and the bucket had no CORS rules, so RustFS answered
without Access-Control-Allow-Origin and the browser blocked the upload.

s3-init now runs put-bucket-cors on every boot after ensuring the bucket
exists (idempotent). Origins are open because the presigned URL is the
credential and the SDK sends no cookies. Document how to re-run and
verify in doc/self-hosting.md.

2026-09-25 12:12:02 -07:00

..

i18n

…

alarms.md

fix(ai): keep per-provider failures when every chat route fails (#3836)

2026-09-09 14:56:11 -07:00

architecture.md

fix: hardening (#3904)

2026-09-18 11:22:39 -07:00

contributing-apis.md

feat: a paid plan counts as a verified card for the sharing gate (#3886)

2026-09-16 10:18:47 -07:00

license_header.txt

…

pagination.md

feat: standardized api pagination (#3412)

2026-07-20 15:58:23 -07:00

self-hosting.md

fix(selfhost): configure bucket CORS in s3-init so browser uploads work (#3934)

2026-09-25 12:12:02 -07:00