convex-domains

作者： get-convex

將您已擁有的網域指向您的 Convex 應用程式（DNS 記錄、自訂網域附加、auth-origin 重新綁定）。

npx skills add https://github.com/get-convex/agent-skills --skill convex-domains
下載 ZIPGitHub
58
試用此 Skill贊助

Set up a custom domain with your own provider

Walk the user's own registrar through pointing their domain at the Convex app: identify the target (hosting or deployment URL), create the DNS records, attach the custom domain, and rebind the auth origin if the app uses auth.

Workflow

  1. Identify the target: the published site host (for *.convex.app static hosting) or the deployment's HTTP actions URL.
  2. Detect an ALREADY-AUTHENTICATED DNS CLI for the user's provider and OFFER to create the records automatically: Cloudflare → flarectl dns create (note: wrangler itself doesn't manage DNS records) or the CF API via their token env; Route53 → aws route53 change-resource-record-sets; Google Cloud DNS → gcloud dns record-sets create; DigitalOcean → doctl compute domain records create; Vercel DNS → vercel dns add. Check auth read-only first (flarectl user info / aws sts get-caller-identity / doctl account get); show the exact commands and get a yes before running.
  3. If no authed CLI (or the user declines), tell the user exactly which records to create at THEIR registrar: the CNAME (or A/ALIAS at the apex) plus the TXT verification record — with concrete host/value strings, not placeholders.
  4. Attach the domain as a Convex custom domain (dashboard or CLI) and wait for verification; note DNS propagation can take minutes to hours. Verify records landed with dig +short.
  5. If the app uses auth (passkeys/OAuth), rebind the auth origin (SITE_URL / RP_ID / ORIGIN env vars) to the new domain and re-deploy/re-publish.
  6. Verify: the domain serves the app over HTTPS, including the apex → www redirect if configured.

Rules

  • Never ask for or handle registrar credentials. A CLI already authenticated on the user's machine is fine — the credential stays in the tool; never install a CLI or run its login/auth flow for this, and never echo tokens.
  • DNS changes on a live domain are user-visible: show the exact commands and confirm before running them; verify afterwards with dig.
  • Always include the TXT verification record, not just the CNAME.
  • Rebinding the domain changes the auth origin — re-publish after, or sign-in breaks.

來自 get-convex 的更多技能

convex-performance-audit
get-convex
審計Convex在讀取、訂閱、寫入競爭及函數限制方面的效能。適用於功能緩慢、洞察發現、OCC衝突或讀取放大等情況。
developmentdatabasedata-analysis
convex
get-convex
將一般 Convex 請求路由至正確的專案技能。當使用者詢問該使用哪個 Convex 技能，或給出未明確指定的 Convex 應用任務時使用。
developmentdatabase
convex-setup-auth
get-convex
設定 Convex 驗證、身份映射與存取控制。用於 Convex 應用中的登入、驗證提供者、使用者資料表、受保護函式或角色。
developmentdatabaseapi
convex-quickstart
get-convex
建立或將 Convex 加入應用程式。適用於新的 Convex 專案、npm create convex@latest、前端設定、環境變數，或首次執行 npx convex dev。
developmentdatabase
convex-migration-helper
get-convex
使用 widen-migrate-narrow 和 @convex-dev/migrations 規劃 Convex 架構與資料遷移。適用於破壞性架構變更、資料回填、資料表重塑或零停機部署。
developmentdatabase
convex-create-component
get-convex
構建可重複使用的 Convex 元件，包含獨立的資料表與面向應用程式的 API。適用於新元件、可重複使用的後端模組、整合或元件邊界工作。
developmentdatabase
convex-migrate
get-convex
使用 @convex-dev/migrations 在已部署的 Convex 應用程式上遷移 schema 並回填資料。
developmentdatabase
convex-optimize
get-convex
審計並優化現有的 Convex 應用程式：安全性、擴展性、升級與可觀測性。