尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Next.js (App Router, TypeScript) + Supabase + Vercel.
• Framework: Next.js 15 (App Router) + TypeScript + Tailwind CSS
• Database / Auth: Supabase (@supabase/ssr)
• Hosting: Vercel
• Package manager: npm
Two separate Supabase projects keep staging data fully isolated from
production. The same SQL migrations are applied to both to keep schemas identical.
1. Copy env template and fill in your staging Supabase keys:檢視完整 README ↗Next.js (App Router, TypeScript) + Supabase + Vercel.
@supabase/ssr)| Environment | Git branch | Vercel target | Supabase project |
|---|---|---|---|
| Local dev | any | — | fusion-studio-staging (or local Supabase) |
| Staging | staging | Preview | fusion-studio-staging |
| Production | main | Production | fusion-studio-prod |
Two separate Supabase projects keep staging data fully isolated from production. The same SQL migrations are applied to both to keep schemas identical.
cp .env.example .env.local
# then edit .env.local
npm run dev
App runs at http://localhost:3000| Variable | Where | Notes |
|---|---|---|
NEXT_PUBLIC_SUPABASE_URL | client + server | Project URL |
NEXT_PUBLIC_SUPABASE_ANON_KEY | client + server | Public anon key |
SUPABASE_SERVICE_ROLE_KEY | server only | Never expose to the browser |
NEXT_PUBLIC_SITE_URL | client + server | Base URL for redirects |
import { createClient } from "@/lib/supabase/client"import { createClient } from "@/lib/supabase/server"src/proxy.ts (this Next.js version renamed the middleware convention to proxy).supabase migration new <name> # create a migration
supabase db reset # rebuild LOCAL db from migrations
supabase link --project-ref <ref> # link a remote project
supabase db push # apply migrations to the linked remote project
Apply the same migrations to staging first, then production.
staging → Vercel Preview deploy (uses staging Supabase env vars).main → Vercel Production deploy (uses production Supabase env vars).