services/backend has a working Dockerfile, auto-runs its own migrations on boot, and honors $PORT/BIND_ADDR — but isn't deployed anywhere yet. Without it, the frontend's indexer-backed features (e.g. sponsorImpact, live stream data) silently fall back to empty/stub data.
To do: deploy to Railway or Render (see repo docs / recent deploy discussion for exact steps), provision Postgres, generate a real JWT_SECRET (openssl rand -hex 32 — do not ship the dev-only-change-me default), and set NEXT_PUBLIC_BACKEND_BASE_URL on the Vercel frontend project to point at it.
services/backendhas a workingDockerfile, auto-runs its own migrations on boot, and honors$PORT/BIND_ADDR— but isn't deployed anywhere yet. Without it, the frontend's indexer-backed features (e.g.sponsorImpact, live stream data) silently fall back to empty/stub data.To do: deploy to Railway or Render (see repo docs / recent deploy discussion for exact steps), provision Postgres, generate a real
JWT_SECRET(openssl rand -hex 32— do not ship thedev-only-change-medefault), and setNEXT_PUBLIC_BACKEND_BASE_URLon the Vercel frontend project to point at it.