add-custom-domain
FeaturedAdd a custom domain to a Temps project and provision an automatic SSL/TLS certificate via Let's Encrypt, driven entirely from the `@temps-sdk/cli` CLI. Handles subdomains, apex domains, HTTP-01 and DNS-01 challenges, and wildcard domains. Use when the user wants to: (1) Add a custom domain to their Temps app, (2) Set up HTTPS/SSL for a deployment, (3) Point their own domain at a Temps project, (4) Add a wildcard domain, (5) Configure DNS for Temps. Triggers: "add custom domain", "point my domain at temps", "set up ssl", "https for my app", "wildcard domain", "add domain to project".
Install
Quality Score: 92/100
Skill Content
Details
- Author
- gotempsh
- Repository
- gotempsh/temps
- Created
- 10 months ago
- Last Updated
- today
- Language
- Rust
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
custom-domain
Point a custom domain at an already-deployed site, end to end: add the domain at the host, create the DNS records at the registrar, fix the settings that break silently when the address changes (auth authorized domains, OAuth redirect URIs, captcha/App Check domain lists, CORS and CSP allowlists), move the site's canonical URL, wait out certificate issuance, and add the www redirect. Use this whenever the user says they bought, registered, or own a domain; whenever they ask to hook up, connect, point, attach, set up, or "use my own" domain, URL, or address for a site; whenever they mention DNS records, nameservers, A/CNAME/TXT records, SSL or HTTPS not working on a new domain, or a domain stuck "pending", "not verified", or "needs setup"; and whenever a site currently lives on a platform subdomain (*.web.app, *.pages.dev, *.vercel.app, *.netlify.app, *.github.io) and they want it somewhere nicer. Also use it when a domain "works but login broke" or "shows the wrong URL in Google" after a move.
connect-domain
Connect a user's own custom domain (subdomain e.g. recipes.brand.com via CNAME, or apex e.g. brand.com via A record) to a site already deployed on simple-host. Use when a user wants their site served from their own domain over HTTPS, or wants sign-in on saves from a page (a domain is what adds sign-in to saves; on the shared host anyone can read and write). Drives the bind → DNS → verify → live flow; the agent does the API work and relays the one DNS record the human must add at their registrar.
custom-domain
Connect a domain of their own to the person's site. Covers registrar selection, current registration and renewal prices, DNS, redirects, and HTTPS. Use when they say "I want my own domain", "get rid of the .github.io part", or "connect mysite.com".