Gitea raw file responses do not send Access-Control-Allow-Origin, so
browser fetches from the Vercel-served status page were blocked
cross-origin. Add a Vercel rewrite that maps /data/(.*) ->
git.moleculesai.app/molecule-ai/molecule-ai-status/raw/branch/main/$1
so the browser only sees same-origin requests; Vercel handles the
upstream fetch server-side and returns the body to the browser.
Tradeoff
- Adds one network hop (browser -> Vercel edge -> Gitea -> Vercel ->
browser). Vercel caches per the Cache-Control: public, max-age=60
header on /data/, so steady-state is one upstream hit per minute
per file. Acceptable.
- Decouples the page from Gitea CORS posture — if/when Gitea ships
Access-Control-Allow-Origin headers (probably correct
long-term), the page can be flipped back to direct fetch by
removing the rewrite.
What did NOT change: probe binary, cron, file paths in history/,
.upptimerc.yml. The data flow is identical; only the URL the
browser uses changed.
0440dc809f