taubyte-local-host-launch（taubyte 本地主机启动）

Local Host Launch

When to use

Use this skill after domain/resource creation in Dream/local when the goal is to:

• access website/function endpoints by FQDN
• open resources in browser using hostnames
• validate host-based routing

Prerequisites

• taubyte-dream-local-operations
• taubyte-hosts-file-editor

Steps

1. Confirm Dream and universe are running: dream status universe default
2. Get FQDN(s) from domain resources: tau query domain --name <domain-name>
3. Ensure hosts mappings exist for each FQDN:

- 127.0.0.1 <fqdn> - run taubyte-hosts-file-editor automatically (do not wait for user prompt)

1. Ensure local deploy trigger is executed for Dream/local: docker info dream inject push-all --universe default

- if docker info fails, stop and report Docker as runtime blocker

1. Discover serving port:

- Usually from substrate: dream status substrate - If gateway is used in the universe, use its HTTP port from dream status universe <name>.

1. Validate by hostname: curl "http://<fqdn>:<port>/<path>"
2. If hosts edit is not available, fallback validation: curl --resolve "<fqdn>:<port>:127.0.0.1" "http://<fqdn>:<port>/<path>"
3. For browser launch:

- open http://<fqdn>:<port>/<path>

Output contract

• Always return:

- exact website URL(s), - exact function URL(s), - one ready-to-run curl per endpoint, - whether hosts mapping was auto-applied or requires manual admin edit.

Notes

• Hosts mappings are OS-level and affect browser resolution.
• curl --resolve is request-scoped and does not modify system DNS.
• For HTTPS tests, prefer --resolve so hostname/SNI stays correct.
• Do not introduce --generated-fqdn-prefix unless the user explicitly asks for a prefix.
• If a function was created with --template empty, ensure empty.go is implemented before launching local tests.