← ConvexCONTENT HISTORY

Update to Convex

Snapshot Sep 30, 2026 · 22:46 UTC · version 2.0.1

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Wire a domain the user ALREADY OWNS (GoDaddy/Namecheap/Cloudflare/…) to their Convex app: exact DNS records, custom-domain attachment, auth-origin rebind. TRIGGER when the user owns a domain and wants it pointing at their app ('point my domain at this', 'use my own domain', 'set up example.com'). Never asks for registrar credentials.",
  "included_files": [],
  "name": "domains",
  "skill_md_contents": "---\nname: domains\ndescription: \"Wire a domain the user ALREADY OWNS (GoDaddy/Namecheap/Cloudflare/…) to their Convex app: exact DNS records, custom-domain attachment, auth-origin rebind. TRIGGER when the user owns a domain and wants it pointing at their app ('point my domain at this', 'use my own domain', 'set up example.com'). Never asks for registrar credentials.\"\nlicense: Apache-2.0\n---\n\n# Custom domain with your own provider ($domains)\n\nPoint a domain the user already owns at their Convex app. No purchase, no\nregistrar credentials — you give the user the exact records to create themselves.\n\n## Procedure\n\n1. **Identify the target:** the published site host (for static hosting) or the\n   deployment's HTTP actions URL (`npx convex env get CONVEX_SITE_URL` or the\n   dashboard).\n2. **Give the exact DNS records** to create at THEIR registrar: the CNAME (or\n   A/ALIAS at the apex) plus the TXT verification record — concrete host/value\n   strings, not placeholders.\n3. **Attach the custom domain** on Convex (dashboard → deployment → Custom\n   Domains, or the CLI) and wait for verification. DNS propagation can take\n   minutes to hours — tell the user, don't poll forever.\n4. **If the app uses auth** (passkeys/OAuth), rebind the auth origin\n   (`SITE_URL` / `RP_ID` / `ORIGIN` env vars) to the new domain and re-deploy —\n   otherwise sign-in breaks on the new domain.\n5. **Verify:** the domain serves the app over HTTPS, including the apex → www\n   redirect if configured.\n\n## Rules\n\n- Never ask for registrar credentials — the user creates the records.\n- Always include the TXT verification record, not just the CNAME.\n- Rebinding the domain changes the auth origin — re-deploy after, or sign-in breaks.\n"
}

SHA-256 of public snapshot: 9ea25f0fd1837e4fd2c47f4406e005f43d432481ff6fbbee2def9f2d90dffba9