尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
依最近已完成的 8 小時觀測回合間的 GitHub 星號增量排序
Type the product name from the box. Bygga shows every assembly step in 3D, with the parts, screws and tools for each one, and reads it out loud.
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權，自行管理介紹，無需管理員核准。
登入並產生驗證檔案，在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案，即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入，將前往登入頁面。登入後請回到此處，再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify，即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗A Melbourne-first curated creative events discovery and ticketing marketplace.
docs/supabase-setup.md for the go-live steps.docs/architecture.md: data model, API and
payment flow.docs/PROJECT_CONTEXT.md: business, legal
and roadmap context.Public, no account needed:
/: curated event feed with category, date and free/paid filters./map: Scene Map./events/[slug]: event details and guest checkout. Free tickets are
issued instantly; paid tickets are paid for on /checkout/pay, in
Stripe's embedded checkout form./checkout/success: order confirmation with ticket codes, also emailed
to the buyer. An oversold order is refunded automatically.Accounts: /signup, /verify, /login, /forgot-password.
Organisers (need an admin-approved application):
/organisers/apply: apply, see your status, and edit and resubmit if
rejected./dashboard: event drafts, an optional event photo, ticket types with
a live fee preview, and submitting for review./dashboard/payouts: Stripe Connect onboarding.Admins: /admin/organisers and /admin/events are review queues
(approve, reject with a reason, unpublish).
Demo mode (no setup, sample data only):
npm install
npm run dev
Live mode: copy .env.example to .env.local and fill it in from your
Supabase project and Stripe test account (see docs/supabase-setup.md).
With the Supabase variables set, the app uses the real API; without them,
it falls back to demo mode.
npm run dev # dev server
npm run build # typecheck + production build
npm run lint # eslint
npm test # unit + API tests (API tests run against in-process Postgres)
npm run test:e2e # Playwright browser tests
npm run test:journey # opt-in end-to-end journeys over HTTP (JOURNEY=1 + TEST_DATABASE_URL; docs/testing.md)
npm run promote-admin -- [email protected] # grant admin (needs SUPABASE_SECRET_KEY)
npm run seed-dev-data # load sample events into a dev database
TEST_DATABASE_URL=postgres://user@host:port/db npm test runs the API tests
against a real Postgres server through the production driver instead of
PGlite. Each test file creates its own throwaway database.
What each test layer covers, and the checks that still need a person
(Stripe test mode, real email, real phones): docs/testing.md.
app/ pages, plus app/api/** route handlers
components/ UI
lib/api/ browser client for the API
lib/auth/ Supabase Auth in the browser
lib/server/ API logic: handlers, validation, SQL, wiring
supabase/migrations/ database schema — apply in filename order
scripts/ admin promotion, dev seed data
tests/, e2e/ vitest (incl. tests/server API tests), Playwright