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).