DOCUMENTATION

Start where you are.

Tebako is a packaging and loading ecosystem: payloads stitched onto a bootstrap, runtimes downloaded once and mounted — never extracted. What you need from these docs depends on which of those you touch.

I RUN PACKAGES

Run a tebako package

Download, install, run — no toolchain, no compilation, no libraries to fetch. Shims put packaged commands on your PATH with per-invocation version dispatch.

I SHIP DATA

Build a data payload

A directory and a manifest become a versioned, mountable .tfs image — fonts, datasets, any file tree. No compilation machinery required.

I SHIP APPS

Package an application

Press your app into a single executable — lean or fat — then publish it to a registry your users add. You compile only your own code; tebako arrives as binaries.

I HACK ON TEBAKO

Work on tebako itself

The architecture documentation: the three-part package, the driver contract, the store, the chain of trust, the repo map — and the contributor guide.

GUIDES

How-to guides

Task-shaped and copy-paste ready: install, run, press, publish, shim, jail, verify, debug, trace, check, inspect.

ARCHITECTURE

Architecture

Concepts and machinery: packages and payloads, the runtime-as-image model, the VFS, factories, stores, and trust.

REFERENCE

Reference

The CLI surface command by command, environment variables, exit codes, manifest and registry schemas, the spec index.

PLANNED · section in progress

GUIDED PATHS

Prefer to be taught rather than told? The blog carries three tutorial series, each a complete arc from first run to advanced packaging.

5 parts