尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证正在加载完整 README。 以下为已保存的摘录。
A campus side-hustle directory MVP for University of Pretoria (Hatfield).
Students list services (hair, nails, tutoring, ...); other students browse,
compare prices, read reviews, and contact sellers on WhatsApp.
Renaming: the product name lives in one place, config.ts (APP_NAME).
• Next.js (App Router) + TypeScript
• Tailwind CSS
• Supabase (Postgres, Auth, Storage, RLS)
• Zod
• Hosted on Vercel
2. Copy the env template and fill in your Supabase project's values
(Project Settings > API in the Supabase dashboard):查看完整 README ↗A campus side-hustle directory MVP for University of Pretoria (Hatfield). Students list services (hair, nails, tutoring, ...); other students browse, compare prices, read reviews, and contact sellers on WhatsApp.
Renaming: the product name lives in one place, config.ts (APP_NAME).
npm install
cp .env.example .env.local
supabase/migrations/0001_init.sql against your
Supabase project (paste it into the SQL editor, or supabase db push
if you're using the Supabase CLI locally).npm run seed
This requires SUPABASE_SERVICE_ROLE_KEY in .env.local and creates
fake auth users ([email protected]) plus seller profiles.
Never run this against a production project — the script refuses
to run when NEXT_PUBLIC_SUPABASE_URL points at the production project.npm run dev
| Variable | Where it's used |
|---|---|
NEXT_PUBLIC_SUPABASE_URL | Browser + server Supabase clients |
NEXT_PUBLIC_SUPABASE_ANON_KEY | Browser + server Supabase clients (RLS-scoped) |
SUPABASE_SERVICE_ROLE_KEY | Server-only: seed script, future admin actions. Bypasses RLS — never expose to the browser. |
All app-wide constants (name, active categories, upload limits) live in
config.ts.
There is no student email verification by design: every signup is treated
as verified (see the handle_new_user trigger in migration 0005).
SQL lives in supabase/migrations/, applied in filename order. Each file
is a plain SQL script — apply it via the Supabase SQL editor or the
Supabase CLI.