尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證deepgram test
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
• Host start/end APIs and host WebSocket publishing are protected by hostToken. • Set a per-org token in Firestore at organizations/{orgId}.hostToken (and/or HOST_API_TOKEN as global token accepted across orgs). • Host dashboard page: /host/c/{churchSlug} now has a Host Token input. • Listener URL remains stable: /c/{churchSlug}/s/{serviceKey}. • In-memory dev backend seeds demo and arkchurch slugs by default. Backend now requires explicit CORS origins (no wildcard *):檢視完整 README ↗
Production security runbook: PRODUCTION_SECURITY.md
Debug UI traffic:
localStorage.setItem("rt_debug", "1");
location.reload();
hostToken.organizations/{orgId}.hostToken (and/or HOST_API_TOKEN as global token accepted across orgs)./host/c/{churchSlug} now has a Host Token input./c/{churchSlug}/s/{serviceKey}.demo and arkchurch slugs by default.Backend now requires explicit CORS origins (no wildcard *):
# backend/.env
CORS_ALLOW_ORIGINS=http://localhost:3000,http://127.0.0.1:3000
http(s)://host[:port]).localhost/127.0.0.1 on ports 3000 and 5173./signup/login/onboarding/create-church/login if unauthenticated./c/{churchSlug}/s/{serviceKey}), no listener login required.If billing is not configured yet and you need to keep testing:
# backend env
DISABLE_BILLING_LIMITS=1
# one or more Firebase Auth UIDs (comma-separated)
MASTER_USER_UIDS=your_firebase_uid
# or single value:
# MASTER_USER_UID=your_firebase_uid
# Optional: lock billing controls to specific account(s)
[email protected]
# BILLING_ADMIN_UIDS=your_firebase_uid
DISABLE_BILLING_LIMITS=1 skips monthly cap enforcement (hardCapReached).MASTER_USER_UIDS gives global owner-level access across organizations.BILLING_ADMIN_EMAILS/BILLING_ADMIN_UIDS (if set) override default behavior and restrict billing settings access to those identities only.super_admin=true to your admin account instead of long-lived env UID lists.Per-org toggle (recommended for temporary exceptions):
/host/c/{churchSlug}?section=settings and use the Billing Limits card.GET/POST /api/auth/org/{orgId}/billing-limits with { "enabled": true|false }.Frontend visibility lock (optional, UX-only):
# frontend env
[email protected]
Sermon Prep now tracks OpenAI token usage per org and per sermon (sermon_id) and can enforce a monthly USD cap.
# Optional monthly default cap per org (0 = disabled)
SERMON_PREP_DEFAULT_BUDGET_USD=0
# Optional kill switch (1 = disable Sermon Prep budget enforcement globally)
# DISABLE_SERMON_PREP_BUDGETS=1
# OpenAI cost rates used for estimation (defaults shown)
SERMON_PREP_INPUT_COST_PER_MILLION=0.15
SERMON_PREP_OUTPUT_COST_PER_MILLION=0.60
/host/c/{churchSlug}?section=settings in the Sermon Prep Budget card.GET /api/org/{orgId}/sermon/usagePOST /api/org/{orgId}/sermon/budget with { "budget_usd": number }402 with detail sermon_prep_budget_reached.Use the guarded admin script (custom claim + audit JSON output):
cd backend
# grant
python scripts/set_super_admin.py \
--grant \
--uid your_firebase_uid \
--actor [email protected] \
--reason "on-call billing admin" \
--ticket SEC-123 \
--audit-log ./logs/god-mode-audit.jsonl \
--yes
# or resolve by email
python scripts/set_super_admin.py \
--grant \
--email [email protected] \
--actor [email protected] \
--reason "on-call billing admin" \
--ticket SEC-123 \
--audit-log ./logs/god-mode-audit.jsonl \
--yes
# check status
python scripts/set_super_admin.py --status --uid your_firebase_uid
python scripts/set_super_admin.py --status --email [email protected]
# revoke
python scripts/set_super_admin.py --revoke --uid your_firebase_uid --actor [email protected] --ticket SEC-123 --yes
super_admin.GOOGLE_APPLICATION_CREDENTIALS (or pass --credentials) for Admin SDK access.Add to frontend/.env.local:
NEXT_PUBLIC_FIREBASE_API_KEY=...
NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN=...
NEXT_PUBLIC_FIREBASE_PROJECT_ID=...
NEXT_PUBLIC_FIREBASE_APP_ID=...
NEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID=... # optional
NEXT_PUBLIC_FIREBASE_STORAGE_BUCKET=... # optional
# Local-only convenience: bypass the host dashboard email verification gate.
# Never set this in production.
# NEXT_PUBLIC_SKIP_EMAIL_VERIFICATION=1
When NEXT_PUBLIC_SKIP_EMAIL_VERIFICATION=1, local signup/login can access the host dashboard without clicking a verification link.
Add to the backend deployment environment:
RESEND_API_KEY=...
PASSWORD_RESET_FROM_EMAIL="Worship <[email protected]>"
RESEND_FALLBACK_FROM_EMAIL="Worship <[email protected]>"
PASSWORD_RESET_CONTINUE_URL=https://www.worshiptranslation.com/login
PASSWORD_RESET_BRAND_NAME="Worship Translation"
FIREBASE_ADMIN_CREDENTIALS=/abs/path/to/firebase-adminsdk.json
If PASSWORD_RESET_FROM_EMAIL is not set, the backend falls back to CONTACT_FROM_EMAIL.
FIREBASE_ADMIN_CREDENTIALS should point to a Firebase Admin SDK service account with Firebase Auth permissions. If it is not set, the backend falls back to GOOGLE_APPLICATION_CREDENTIALS.
If your custom sender domain is not verified in Resend yet, RESEND_FALLBACK_FROM_EMAIL can temporarily use [email protected].
Use one canonical env for live translation:
OPENAI_TRANSLATION_MODEL=gpt-4o
Optional sermon-only override:
OPENAI_SERMON_TRANSLATION_MODEL=gpt-4o-mini
Compatibility note:
OPENAI_TRANSLATION_MODEL is preferred for the live translation path.OPENAI_SERMON_TRANSLATION_MODEL is preferred for sermon prep/script translation.TRANSLATION_MODEL, OPENAI_MODEL, and OPENAI_SERMON_MODEL still work as fallbacks.Seed one org + default services:
cd backend
python scripts/bootstrap_multichurch.py \
--org-id arkchurch \
--slug arkchurch \
--name "Ark Church" \
--service sun-11am:"Sunday 11 AM" \
--service sun-2pm:"Sunday 2 PM"
Outputs include the generated hostToken.
Re-running bootstrap now reuses the existing org hostToken unless --host-token is provided explicitly.
backend/firestore/firestore.rulesbackend/firestore/firestore.indexes.jsonThe existing Deepgram + GPT engine remains the default. To enable the optional Gemini 3.5 Live Translate preview engine, configure the backend:
GEMINI_API_KEY=your_google_ai_api_key
GEMINI_LIVE_TRANSLATE_MODEL=gemini-3.5-live-translate-preview
Hosts can then select Gemini 3.5 Live Translate (preview) under Advanced
Controls. The API key stays on the backend. Gemini transcripts reuse the
existing room broadcast protocol, and supported listener pages play Gemini's
translated PCM audio when their Audio control is enabled.