尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗A private web app (PWA) for a group of friends who meet to play board games: browse the game catalog, vote on what to play before a session, log each play, keep group photos, and review history and stats.
Live at https://alvaro2b.vercel.app (Members only).
git clone https://github.com/panicoenlaxbox/alvaro2b.git
cd alvaro2b
pnpm install
pnpm supabase start
Then copy .env.example to .env.local and fill it in with two values that pnpm supabase start prints (or pnpm supabase status, at any time):
NEXT_PUBLIC_SUPABASE_URL: Project URL, in the APIs box (http://127.0.0.1:54321).NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY: Publishable, in the Authentication Keys box (sb_publishable_…). Finally:pnpm dev
Supabase Studio, to browse the local database, is at http://localhost:54323.
Stop the stack with
pnpm supabase stopbefore quitting Docker: its containers restart with Docker unless they were stopped.
Curious about what we play? Brace yourself for some envy: the group's collection, 34 Games and 5 Expansions, lives in supabase/seed/catalog.sql.
main to https://alvaro2b.vercel.app (region dub1, next to Supabase in eu-west-1). There are no previews or staging. Production variables: NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY and CRON_SECRET.alvaro2b.insert into public.allowed_emails (email, is_admin) values ('[email protected]', true); in the SQL Editor.vercel.json) calls /api/keep-alive, which runs a real query. It is a Vercel cron and not a scheduled GitHub Actions workflow because GitHub disables scheduled workflows after 60 days without repository activity, exactly when the keep-alive matters most. If Supabase emails a pause warning, the keep-alive is not working.