tb_cmd_tau_new_domain_generated_fqdn
Command card
Preconditions: Cloud context verified via tau --defaults --yes json current.
Forbidden (unconditional): Do not pass --generated-fqdn-prefix, --g-prefix, or any CLI synonym for a generated-FQDN prefix to tau new domain — ever, including if the user asks. See tb_sys_core_constraints and tb_sys_resource_flags_reference → Domain generation.
Command:
tau --defaults --yes new domain --name <domain> --generated-fqdn --type auto --description "<desc>"
Postconditions: Update context log.
Critical note: Generated FQDN shape depends on the currently selected cloud. Confirm remote context before creating domains intended for remote (Cloud Type: remote, expected cloud FQDN). Do not generate while Dream is selected when remote DNS behavior is required.
Rules: tb_sys_core_constraints, tb_sys_execution_modes (default: tau --defaults --yes).
More from taubyte/skills
verifying-taubyte-functions
Verifies a Taubyte Go function locally via the `taubyte/go-wasi` Docker recipe (preferred over `tau build`, with tmpfs+bind-mount-ro to avoid root-owned artifacts in the source tree), and verifies a function actually serves on Dream by curling the gateway with the right `Host:` header (plus `/etc/hosts` mapping for `*.localtau`). Use when locally compiling a Go function to WASM, when smoke-testing a function before pushing, or when probing a Dream-hosted HTTP function from the laptop.
12creating-taubyte-resources
Creates Taubyte resources non-interactively via `tau new` for domain, website, library, function, application, database, storage, messaging, and service. Encodes the project-vs-application scope rule, the database `min < max` constraint, the website/library `--generate-repository` + import sequence, and the forbidden `--generated-fqdn-prefix` flag. Use when adding any resource to a Taubyte project's config repo.
12diagnosing-dream-builds
Diagnoses Dream local-cloud builds when `tau list/query builds` is empty or unreliable, by hitting the jobs HTTP endpoint directly (`GET /jobs/<project_id>`, `GET /job/<job_id>`) using the GitHub token from `~/tau.yaml`, then downloading logs with `tau query logs --jid`. Use when Dream builds appear silent, the build table is empty after `dream inject`, or you need raw job ids and logs for a failing build.
11taubyte-resource-creation
Scope-aware resource creation workflow. Uses non-interactive mode by default and references the shared flags catalog.
11taubyte-push-build-verify
Pushes config/code and verifies builds/logs. Includes website/library push handling with tau command first, git fallback.
11taubyte-scope-routing
Routes project-level vs application-scoped work; defaults to a website when a browser UI is logically appropriate; avoids unnecessary applications for simple website/function-only tasks unless needed.
11