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

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.