add-custom-domain

Add a Custom Domain

Add a custom domain to a Temps project and get automatic HTTPS. This skill drives the whole flow from the CLI; the human equivalent is Project → Domains → Add Domain in the dashboard.

When to use

The user wants their own domain (e.g. app.example.com) serving a Temps project, with an SSL certificate, instead of the auto-assigned subdomain.

Prerequisites

• The Temps CLI is authenticated. Verify, and log in to the user's instance if needed (login is a top-level command; the instance URL is the positional argument):

  bunx @temps-sdk/cli whoami || bunx @temps-sdk/cli login "<instance_url>"
  

• The user knows the domain to add and which project it belongs to.
• The user can edit DNS for the domain (or has a DNS provider connected in Temps for DNS-01 / wildcard).

First: does a tunnel already cover the domain?

If the apps run on workers with an ingress tunnel (ADR 058), the domain needs no DNS record and no certificate: Temps creates the record and the tunnel's provider serves HTTPS. Check before anything else:

bunx @temps-sdk/cli tunnels list --json
bunx @temps-sdk/cli tunnels explain app.example.com --json

If explain lists a tunnel in candidates (its domain is example.com or a parent of the name):

1. Attach the name to the environment (step 3 below, same command). Do not create a certificate for it: tunnel traffic reaches Temps as plain HTTP, and a local certificate makes the proxy redirect it to HTTPS.
2. If the tunnel publishes only chosen names, or several tunnels cover it, route it explicitly:

   bunx @temps-sdk/cli tunnels route app.example.com --tunnel <tunnel-id>
   

3. Within a minute tunnels explain app.example.com should report published. Its detail says what to fix when it does not (the usual one: no deployed app on a worker serves the name yet).

Cloudflare's free certificate covers the zone and one level below it: app.example.com works, a.b.example.com needs an advanced certificate.

No tunnel yet, but the domain is a zone in a connected Cloudflare DNS provider and the user wants one? Create it on the worker(s) that should carry it (each must allow ingress: temps agent ingress delegated on the worker):

bunx @temps-sdk/cli dns-providers list --json   # the Cloudflare provider id
bunx @temps-sdk/cli tunnels workers --json      # worker ids
bunx @temps-sdk/cli tunnels create --name example-com --dns-provider <id> \
  --domain example.com --node <worker-id> [<worker-id>...]

Otherwise, use the certificate flow:

Steps

1. Identify the project. If the user gave a name but not an ID, list projects and resolve it:

   bunx @temps-sdk/cli projects list --json
   

   Note the numeric id of the target project. Use it as <project-id> below.

2. Create the DNS record at the user's DNS provider so the domain points at the Temps server. Tell the user exactly what to add (you cannot create this for them unless a DNS provider is connected in Temps):

   • Subdomain (app.example.com): A record, name app, value = the server's public IP. A CNAME to the server hostname also works.
   • Apex (example.com): A record, name @, value = the server's IP. (CNAMEs are not allowed at the zone root.)
   • If the user is on Cloudflare, have them set the record to DNS only (grey cloud) during issuance so Temps' Let's Encrypt challenge isn't proxied.

3. Add the domain to the project. Default is the HTTP-01 challenge, handled automatically:

   bunx @temps-sdk/cli custom-domains create --project-id <project-id> -d app.example.com -y
   

   • Apex + Cloudflare/another provider connected, or port 80 not reachable: use DNS-01 instead (see Wildcard below) — confirm a DNS provider is connected in Settings → DNS Providers first.

4. Wildcard domains (*.example.com) require DNS-01 and a connected DNS provider. Confirm the provider is connected, then add the wildcard the same way:

   bunx @temps-sdk/cli custom-domains create --project-id <project-id> -d "*.example.com" -y
   

   Temps creates the _acme-challenge TXT record automatically via the provider.

Verify

bunx @temps-sdk/cli custom-domains list --project-id <project-id>

The domain should progress to active once DNS propagates and the certificate is issued (usually under a minute for HTTP-01). You can confirm DNS independently:

dig +short app.example.com A

If the domain stays pending: verify the DNS record resolves to the server, that port 80 is reachable (HTTP-01), and — on Cloudflare — that the proxy is off during issuance. Certificates renew automatically ~30 days before expiry.

Related

• Dashboard path: Project → Domains → Add Domain
• Doc: https://temps.sh/docs/add-a-custom-domain
• CLI group: bunx @temps-sdk/cli custom-domains --help
• Tunnels: bunx @temps-sdk/cli tunnels --help. Dashboard: Domains → Add Domain offers "Through tunnel …" when one covers the name; importing a zone from a Cloudflare DNS provider offers "Through Cloudflare Tunnel".
• Full CLI reference: the temps-cli skill covers all 440+ bunx @temps-sdk/cli commands.