add-custom-domain

Featured

Add 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".

DevOps & Infrastructure 655 stars 46 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
94
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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): ```bash 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: ```bash 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...

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

AI & Automation Listed

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

1 Updated 1 weeks ago
protosphinx
AI & Automation Listed

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 with automatic HTTPS, or wants a private/password-protected site (privacy is offered only on a connected domain). 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.

1 Updated today
vineetu
DevOps & Infrastructure Featured

temps-cli

Operate Temps through the pinned `@temps-sdk/cli` package with bunx or npx. Use when the user mentions Temps CLI, `@temps-sdk/cli`, a CLI command, or asks to deploy, configure, inspect, automate, or administer Temps from a terminal. Covers contexts, projects, deployments, environments, services, domains, monitoring, backups, telemetry, browser Performance Insights/Core Web Vitals, Cloud, platform administration, and read-only managed-data browsing. Apply the target-context, secret-handling, confirmation, and verification rules for every agentic CLI operation.

655 Updated today
gotempsh