OTO
reference · oto build --help at v0.6.1

oto build

compile every layer

oto build [-h] [--project PROJECT] [--only ONLY] [--skip-preflight] [--no-transaction]
                 [--target TARGET] [--verify] [--view VIEW]

Options

OptionWhat it does
--project PROJECTproject root (default: current directory)
--only ONLYcomma-separated stage names to run (default: all)
--skip-preflightskip validation (for debugging a partial build)
--no-transactionwrite in place; a failure then leaves a partial build
--target TARGETalso load an optional target this time, e.g. neo4j (repeatable)
--verifyafter loading an external target, read it back and compare with the build
--view VIEWfor the site target: the view, by name or directory, to copy beside data.json (default: the built-in explorer)

Where to use it

Compile every layer.

oto build --project claims

ontology, semantic cards, the SQLite store, and the targets the project configures; refused if the graph uses what the ontology does not declare

Load the production store too, and prove it matches.

oto build --project claims --target neo4j --verify

loads Neo4j, reads it back, compares with the build

A static site to host anywhere.

oto build --project claims --target site --view reader

build/site/ with the graph as data and the chosen view beside it

Only one stage, while debugging.

oto build --project claims --only sqlite --skip-preflight

runs one stage without validation; for a partial build you understand

As the terminal prints it
usage: oto build [-h] [--project PROJECT] [--only ONLY] [--skip-preflight] [--no-transaction]
                 [--target TARGET] [--verify] [--view VIEW]

options:
  -h, --help         show this help message and exit
  --project PROJECT  project root (default: current directory)
  --only ONLY        comma-separated stage names to run (default: all)
  --skip-preflight   skip validation (for debugging a partial build)
  --no-transaction   write in place; a failure then leaves a partial build
  --target TARGET    also load an optional target this time, e.g. neo4j (repeatable)
  --verify           after loading an external target, read it back and compare with the build
  --view VIEW        for the site target: the view, by name or directory, to copy beside data.json
                     (default: the built-in explorer)