尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证Social film diary with self-running Movie Clubs — log, rate and review films, then let a weekly random wheel pick what your group watches. Next.js 15 · Drizzle · Postgres · TypeScript.
翻译准备中
取自仓库 README
正在加载完整 README。 以下为已保存的摘录。
Your films. Their films. Our films.
A social film diary, and the Movie Club that runs itself.
It does the things a film-tracking network has to do: log what you watch, keep a
diary worth re-reading, rate and review, build lists and watchlists, follow
people whose taste you trust. Then it adds the part nobody else does properly —
Movie Clubs, where everyone submits one film a week, the wheel picks at
random, and the group gets an email telling them what they're watching.查看完整 README ↗Your films. Their films. Our films.
Nitrate is a social film diary and Movie Club app. Track films, keep reviews and lists, discover people with shared taste, and organize a group from movie ideas through picks, a wheel or vote, scheduling, and post-film discussion.
The local folder is still named LetterCube; the product, repository and
hosting project are Nitrate. Product copy comes from src/lib/brand.ts.
This is a source-backed inventory, reviewed 27 October 2026. Unit/build checks and public HTTP checks have different coverage from signed-in, database, email and physical-device testing. See verification and known gaps, including the unresolved club aggregate blind-rating gap.
| Document | Purpose |
|---|---|
| Features | Implemented workflows and conditional capabilities |
| Status | Current verification evidence and limits |
| Handoff | Setup, environment, migrations, deployment and operations |
| Storage | Safe disk cleanup, recovery and worktree policy |
| Roadmap | Remaining gaps and priorities |
| Design & product | Product principles, surfaces, design and accessibility |
| Product brief | Audience and concise product direction |
| Decisions | Architecture, constraints and historical decisions |
| Club terminology | Member-facing vocabulary |
| Renaming | Brand configuration and infrastructure identifiers |
| Historical releases |
Next.js 15.5.x (App Router), React 19, strict TypeScript, Tailwind CSS 4, PostgreSQL, Drizzle, custom sessions, TMDB, Resend and optional Tenor. Use Node 20 or newer; the lockfile is authoritative for dependency versions.
src/app/ Pages, API routes, server rendering and gated dev fixtures
src/components/ Shared UI and interactive workflows
src/server/ Services, actions, auth, privacy, providers, email and import
src/server/db/ 63 tables in the dedicated nitrate schema
src/lib/ Shared helpers, pure domain logic and brand configuration
drizzle/ Ordered SQL migrations and metadata, 0000 through 0017
scripts/ Deliberate migration and local storage commands
test/ Test guards and storage safety tests
Authorization belongs on the server. Film state changes share one service; rewatches retain independent history. Ratings use integers 1–10 for half stars. The wheel animates a server-committed result; replay does not draw again. Managers can explicitly edit the pool or choose/correct a result before the night is completed, with permission checks and attribution.
npm ci
cp .env.example .env.local
# Set DATABASE_URL and SESSION_SECRET; configure optional providers as needed.
npm run db:migrate # confirm this is the intended development database first
npm run dev
Database migrations are deliberate, never an app startup side effect. Application and migration credentials can target a live shared database: read Handoff before running them.
npm run verify # TypeScript, lint, unit tests, production build
npm run test:storage # Temporary-repository cleanup safety checks
Database integration is separate and opt-in:
# Point TEST_DATABASE_URL at a distinct disposable database first.
npm run db:migrate:test
npm run test:integration
npm run storage:report -- --worktree-dependencies
npm run storage:clean -- --worktree-dependencies
These commands inspect the main checkout and registered worktrees inside
.claude/worktrees/. Cleanup removes generated build/test files and, with the
flag above, duplicate worktree dependencies. It preserves source, dirty work,
Git history, environment files, images and worktree checkouts. To also remove
the main dependency install, add --dependencies, then restore it with npm ci.
See Storage for safeguards and recovery.
Film metadata and artwork are provided by TMDB. This product uses the TMDB API but is not endorsed or certified by TMDB. Released under the MIT License.
| Original 1.3–2.0 dossiers and evidence |
| Design references | Preserved mockups, outside public runtime assets |