Galaxy Movies

Galaxy Movies is an ultra-fast, mobile-friendly discovery platform for film and TV. Track what's coming to and leaving every major streaming service, find where anything is streaming right now, get alerted when something you care about arrives, and ask an AI assistant what to watch next.

Live at galaxymovies.app.

---

✨ Features

• ⚡ Instant Search & Discovery: Browse thousands of trending movies and shows, explore cast, studio, and network pages, and move between views with sub-100ms transitions.

• 📺 Where to Watch: Check exact streaming, rental, and purchase availability for any title across regions (US + India).

• 📈 Streaming Changes: Daily-tracked provider diffs power "new on" and "leaving" pages, monthly arrivals-vs-departures verdicts (/this-month/[provider]), and an open JSON feed at /api/streaming-changes.

• 🔔 Alerts: Email and web-push notifications when a specific title lands on a service, a weekly digest of everything coming/leaving, and an ICS calendar feed. Optional Telegram bot.

• 📖 AI Synopses: Get quick, objective film summaries generated via the OpenAI API before deciding what to watch.

• 🤖 Galaxy Bot: A conversational AI movie assistant designed to eliminate choice paralysis by providing tailored recommendations based on mood, group preferences, time limits, and real-time streaming availability.

• ⭐ Galaxy Plus: Paid subscription (Polar billing) with personalized recommendation digests, Trakt sync, and an ad-free experience.

• 🧩 Embeds & More: Iframe widgets (/embed/[provider]) third-party sites can drop in for daily streaming-change lists, curated lists and collections, plus a trivia game.

• 🌌 Dynamic OG Cards: Generates high-resolution social share cards dynamically using next/og (/api/og, /api/og-leaving).

---

🛠️ Tech Stack & Architecture

• Framework: Next.js 16 (Pages Router) + React 19, strict TypeScript

• Styling: Chakra UI v3 + Framer Motion

• State & Caching: TanStack React Query v5; Upstash Redis (REST) for server-side state

• AI: OpenAI API — chat assistant, synopses, generated list intros

• Data: TMDB API + Watchmode API for streaming availability

• Billing: Polar subscriptions + webhooks

• Email & Push: Resend, web-push (VAPID)

• Infra: Cloudflare Workers via @opennextjs/cloudflare in production; Vercel kept as cold standby

• Quality: Vitest, ESLint flat config, Lighthouse CI budgets

• Analytics: Umami + Google Search Console indexing reports

---

🚀 Development

npm install            # installs deps + applies patch-package patches
npm run dev            # dev server on :3000 (webpack)
npm run typecheck      # tsc --noEmit (TypeScript 7 native)
npm test               # Vitest unit tests
npm run test:coverage  # tests + v8 coverage floor
npm run lint           # ESLint
npm run check          # typecheck + production build

npm run dev:turbo runs Turbopack but currently hits a Next.js Pages Router dev bug — keep dev on webpack.

A husky pre-commit hook runs typecheck + lint + tests.

Environment

Copy .env.local and fill in what you need. TMDB_API_KEY is the only hard requirement for browsing; the rest gate specific features:

Variable	Feature
TMDB_API_KEY	Catalog data (required)
OPENAI_API_KEY	AI synopses, reviews, Galaxy Bot
WATCHMODE_API_KEY	Streaming availability / prices
UPSTASH_REDIS_KV_REST_API_URL + _TOKEN	Caching, rate limits, alerts storage
RESEND_API_KEY / RESEND_FROM	Email alerts + digests
POLAR_*	Plus subscriptions
NEXT_PUBLIC_WEBPUSH_PUBLIC_KEY / WEBPUSH_PRIVATE_KEY	Push notifications
CRON_SECRET	Authenticates /api/cron/*

Social-channel keys (BSKY_*, TELEGRAM_*, X_*, MASTODON_*, SOCIAL_*_WEBHOOK) each gate an optional broadcast channel.

📁 Structure

• src/pages/ — routes (Pages Router); API routes stay thin and call into features
• src/features/{catalog,alerts,billing,ai,social,game,monetize,indexing}/ — domain modules
• src/lib/ — cross-cutting infra (redis, auth, rate limiting, email)
• src/components/ — shared UI
• scripts/ — plain-JS build/deploy tooling
• patches/ — patch-package patches for @opennextjs/cloudflare

☁️ Deployment

Production runs on Cloudflare Workers (galaxymovies.app + www):

npm run cf:build       # webpack build + OpenNext adapter + postbuild
npm run cf:preview     # build + wrangler dev locally
npm run cf:deploy      # build + deploy to the custom domain
npm run cf:secrets     # push .env.local values as worker secrets
npm run smoke          # post-deploy probe against prod
npm run smoke:workerd  # boot the built bundle under wrangler dev + smoke it

Scheduled jobs (streaming-change diffs, watchlist alerts, weekly digest, social broadcasts, content generation, GSC indexing report) run via worker scheduled() triggers.

Vercel is cold standby only — DNS records and git.deploymentEnabled: false in vercel.json keep it ready for instant rollback.

Operational detail lives in AGENTS.md.