尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗One repo, two Next.js apps, one Supabase project behind both.
| Path | Port | What it is |
|---|---|---|
apps/booking | 3000 | Customer-facing. Serves every tenant's booking pages, chosen by hostname, plus /embed.js. Later: /api/agent, webhooks, the jobs runner. No logins. |
apps/admin | 3001 | Owner dashboard (and later super-admin). Everything behind a login. |
packages/core | Shared code: Supabase admin client, tenant lookup, and the booking engine (pricing, availability, holds). | |
supabase/ | Migrations and seed data. |
npm install
npm run dev # both apps, behind one address: localhost:3000
npm run dev:booking # just the booking app, on :3002
npm run dev:admin # just the admin app, on :3001
npm test # unit tests for pricing, availability and time zones
Both apps read the root .env.local (see .env.example). The booking app
needs SUPABASE_SECRET_KEY.
npm run dev starts a small router on :3000 (routing/dev-router.mjs) in front of
the two apps. It applies the same rules as Vercel (routing/rules.mjs, which vercel.json
is written from by npm run routing:vercel), so each address
reaches the app that serves it. Every link is built by packages/core/src/urls.ts
from ROUTING_MODE (see .env.example and info/routing.md).
Path mode (the default, and what the .vercel.app deployment uses):
Subdomain mode (ROUTING_MODE=subdomain and NEXT_PUBLIC_ROUTING_MODE=subdomain;
browsers send *.localhost to your machine without any DNS):
A business's booking pages come from its slug; the domains table only holds
domains of their own (booking.theirsite.co.uk), used in subdomain mode once verified.
Apply migrations to the hosted project with the Supabase CLI
(npx supabase db push), then run supabase/seed.sql in the SQL Editor.
packages/core/src/booking/engine.ts is the tool layer: getBookingConfig
(list_services), quote (get_quote), checkArea, findSlots
(check_availability), saveLead, holdSlot and confirmBooking. The plain
booking form uses it now; the Booking Agent will call the same functions.
Prices only ever come from getQuote() in pricing.ts.