Skip to content

GUIDES · 01

Pick a task, follow the steps.

Each guide is one task: a short explanation, then commands you can paste into a terminal. macOS and Linux are assumed; Windows differences are noted where they exist. The architecture documentation explains the machinery underneath when you want it.

GUIDE 01 · INSTALL

Install tebako

Brew, the shell installer, or a direct binary — plus a first packaged command in about a minute.

GUIDE 02 · RUN

Run a packaged app

Execute the package file itself, drive it with tebako run, or manage it with registries and shims.

GUIDE 03 · PACKAGE

Package a Ruby app

tebako press: lean vs fat, extra slices, baked jail policies, and multi-command suites.

GUIDE 04 · DATA

Create a data payload

A directory and a manifest become a versioned, mountable .tfs image — no toolchain required.

GUIDE 05 · PUBLISH

Publish to your own registry

Your GitHub releases are the storage; tebako publish writes the index your users add.

GUIDE 06 · LIBRARY

Curate a local library

A directory of .tfs artifacts and one YAML index: the file:// registry for on-prem and air-gapped fleets.

GUIDE 07 · SHIMS

Shims & versions

Commands on PATH with per-invocation version dispatch: environment, project file, config, registry.

GUIDE 08 · JAILS

Set a jail policy

Declare what of the host filesystem a run can see — and tighten any invocation.

GUIDE 09 · VERIFY

Verify integrity

SHA-256 anchors, strict signature checks, and signing your own artifacts.

GUIDE 10 · DEBUG

Debug & logging

TEBAKO_DEBUG, per-component levels, doctor, and the exit codes worth memorizing.

GUIDE 11 · INSPECT

info & inspect

Read the store, a package, or the inside of an image — without extracting anything.

GUIDE 12 · TRACE

Trace a packaged app

The interception bus and its front-ends: trace run for discovery, explain for diagnosis, cover for escapes.

GUIDE 13 · CHECK

Check a payload

The in-image checks: block and tebako check — the payload’s own acceptance test, runnable three ways.