Rai220 opens a hosted Mike stand to direct document uploads

A small hosting change lets browsers send files straight to the storage service on Rai220's deployed instance.

intakeinfrastructure

Rai220 has added the hosted site as an explicitly trusted source for browser-based uploads. That removes a common deployment snag: a user selects a document, but the browser refuses to pass it on to hosted storage because the site was not authorised to do so.

This is intentionally narrow. It permits only the upload and file-check actions needed for that hosted stand, rather than opening storage broadly to other sites. It is a deployment fix, not a new Mike capability, and another operator would need to authorise their own trusted domain.

The GitHub change is worth a look for anyone configuring a hosted version of Mike with browser-direct file storage.

So what Hosted legal-product teams should care because reliable document intake depends on this otherwise invisible browser permission.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from Rai220/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

5e0b22a6 chore(storage): allow the hosted stand origin in the bucket CORS rules Крестников Константин Николаевич 2026-09-10 ↗ GitHub

SHA	Subject	Author	Date
`5e0b22a6`	chore(storage): allow the hosted stand origin in the bucket CORS rules	Крестников Константин Николаевич	2026-09-10	↗ GitHub
commit body Direct uploads go from the browser straight to the storage bucket, so every origin the app is served from has to appear in the bucket's CORS rules. The list carried only the two localhost origins, which left uploads failing on any hosted deployment. Add the stand's origin, and expand the file to one entry per line so the next origin is a one-line diff. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit body

Direct uploads go from the browser straight to the storage bucket, so every
origin the app is served from has to appear in the bucket's CORS rules. The
list carried only the two localhost origins, which left uploads failing on any
hosted deployment. Add the stand's origin, and expand the file to one entry per
line so the next origin is a one-line diff.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-2026.md from inside the repo you want the changes in.

⬇ Download capture-thread-2026.md