feat(streaming): standalone media proxy server, footer, and configurable proxy origin

[harusharu]

Summary

This PR makes the streaming app able to play sources from provider CDNs that block Vercel's datacenter IPs (e.g. the Aliyun OSS host behind themoviebox.org returns 403 Forbidden for cloud IPs). It adds a self-contained, Node-only media proxy server that can run on a VPS/home server with a residential IP, reusing the exact same /api/proxy protocol the player already speaks. It also introduces a compact site footer and tidies up a few tooling configs.

What's included

1. Standalone proxy server — server/proxy.ts

• Exposes /api/proxy with the same query contract as the in-function route handler (url + optional referer / origin / userAgent / cookie header params), plus a /health endpoint.
• Reuses proxyStream() from src/lib/media/streamProxy so manifest rewriting and header injection live in one place.
• Supports Range requests, HEAD requests, and cancels the upstream fetch (AbortController) when the client disconnects so long streams don't leak connections.
• Rewrites HLS manifests to absolute URLs pointing back at the proxy origin (new origin option) so segments/keys resolve correctly in the standalone deployment.
• Maps upstream failures to meaningful status codes (passes through 4xx/5xx, defaults to 502).

2. esbuild bundling — scripts/build-proxy.mjs

• Bundles server/proxy.ts into a single self-contained dist/proxy-server.cjs (Node 22 target, @/ alias resolved to src/). The artifact runs with just Node — no node_modules, no Next.js.
• New pnpm scripts: pnpm build:proxy and pnpm start:proxy.
• esbuild added to devDependencies and its build script allowed in pnpm-workspace.yaml (allowBuilds).

3. Configurable proxy origin

• playbackUrl() in src/lib/media/playback.ts now honors NEXT_PUBLIC_STREAM_PROXY_URL. When set, generated media URLs point at the external proxy; when unset, playback stays same-origin (/api/proxy).
• proxiedUrl() / rewriteHlsManifest() in streamProxy.ts accept an origin param to emit absolute rewritten HLS URLs for the standalone deployment.
• .env.example documents the new optional variable.

4. Site footer — src/components/layout/Footer.tsx

• Compact two-row footer with links to the GitHub repo, "Report an issue", and the AGPL-3.0 license, plus a copyright line noting content streams from third-party providers.
• Rendered once from App.tsx, animated with the existing viewFadeUp / VIEWPORT primitives.

5. Tooling & housekeeping

• biome.json: ignore the .agents directory (vendored skill data shouldn't be linted/formatted).
• .gitignore: ignore dist/ (proxy build artifact).
• next-env.d.ts: refreshed to the .next/types route types.
• skills-lock.json + pnpm-lock.yaml regenerated.
• Skill data fixtures under .agents re-generated by their update tooling (large data churn is expected/intentional).

Testing / how to verify

• Same-origin path (unchanged): run pnpm dev — playback uses /api/proxy as before. No behavior change without env config.
• Standalone proxy path:

  pnpm build:proxy
  NODE_ENV=production PORT=8787 node dist/proxy-server.cjs
  curl -s "http://localhost:8787/health"   # -> {"ok":true,"service":"harustream-proxy"}

  Then point the app at it with NEXT_PUBLIC_STREAM_PROXY_URL=https://your-host.example.
• Run pnpm typecheck and pnpm lint to confirm nothing regressed.

Notes

• No breaking changes; existing deployments are unaffected unless the new env var is set.
• The proxy must run behind a public origin (real hostname/TLS) for absolute HLS URL rewriting to work from the browser.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
harustream	Ready	Preview	Aug 20, 2026 9:47am

[harusharu]

Abandoning this approach; will rework streaming proxy strategy separately.