尚未偵測到更新。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.