Loading...
Loading...
Found 21 Skills
Deploy/self-host Taubyte cloud with @taubyte/spore-drive SDK using code-first automation and minimal required user input.
Launch and verify Dream local resources by hostname using hosts mappings and universe/substrate ports.
Manages server-side build/runtime via `.taubyte/build.sh` and `.taubyte/config.yaml`; env vars live in build.sh only. Website build.sh is stack-specific (Vite vs CRA/React, etc.). Documents GitHub → webhook vs Dream inject (push-all / push-specific).
Creates/selects project; creates or selects an application only when scope or task requires it—not for simple website/function-only work.
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.
Scope-aware resource creation workflow. Uses non-interactive mode by default and references the shared flags catalog.
Must-use go-sdk API shapes to avoid Taubyte compile/build failures for HTTP, PubSub, and Storage functions.
Non-negotiable Taubyte constraints that prevent config/build/runtime failures.
Hard gate before any Taubyte workflow — Node.js and Docker (install when possible), @taubyte/cli and @taubyte/dream via npm, auth per taubyte-auth-and-profile. Version checks and hard stops.
Routes project-level vs application-scoped work; avoids creating or selecting an application for simple website/function-only tasks unless needed.
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.
Handles Taubyte login/profile setup and first-time browser GitHub auth via tau login --new when no account exists; tau login for existing profiles. Stops immediately when browser login is required. Uses non-interactive login when the user supplies a GitHub username; otherwise asks for it explicitly. Must run before cloud/project/resource operations.