Configuring Taubyte Build & Runtime

When to use

• Adding a .taubyte/build.sh to a function/website/library repo for the first time
• Switching the build image (e.g. taubyte/go-wasi:latest → taubyte/go-wasi:v2)
• Declaring environment variables that the build needs to see
• A website builds but serves nothing (empty /out)
• A function compiles to WASM but the runtime sees an empty / wrong env value
• The build script for one stack (Vite) was copy-pasted onto another (CRA) and now the bundle output isn't found

The two files (every Taubyte buildable resource has them)

<resource>/
└── .taubyte/
    ├── config.yaml      # image + workflow metadata (NOT env vars)
    └── build.sh         # the actual build script (where env vars live)