talead 0.1.0

The talea ledger daemon: init (migrate, generate token, seed, write .env) and serve
docs.rs failed to build talead-0.1.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

talead

The talea ledger daemon. Two subcommands; zero-to-serving in two of them.

cargo run -p talead -- init        # migrate, generate an API token, apply seed, write .env
cargo run -p talead -- serve       # serve http://127.0.0.1:8080 using .env

talead init

Idempotent setup, safe to re-run:

  • Connects to --db-url (default sqlite://talea.db; also takes postgres://... or log://<dir>) and runs migrations where the backend has them.
  • Generates a random API token and writes .env (TALEA_DB_URL, TALEA_API_TOKEN). An existing .env is left untouched unless --force.
  • Applies a declarative seed when talea.seed.toml exists (see talea.seed.example.toml at the workspace root): assets and accounts in TOML, applied idempotently on every run — already-present entries are counted, not errored.
talead init [--db-url <url>] [--seed <path>] [--env-out <path>] [--force]

talead serve

Loads .env if present (real environment variables win), then runs the server from talea-server: axum REST + SSE, bearer auth, admission control. Configuration:

Variable Default Meaning
TALEA_DB_URL required postgres://..., sqlite://path.db (:memory: is rejected), or log://<dir>
TALEA_BIND 127.0.0.1:8080 Listen address
TALEA_API_TOKEN unset Bearer token; unset means OPEN dev mode (logged loudly)
TALEA_DB_POOL 10 Connection pool size
TALEA_MAX_INFLIGHT 256 In-flight request cap; excess sheds as 503
TALEA_HTTP_BATCH_MAX 500 Max drafts per POST /v1/transactions/batch request
TALEA_LOG_* unset Append-log store tuning (snapshot cadence, idem cap, segment size) — see talea-store-log

Talk to it with the talea CLI or SDK from talea-client. See the workspace README for a full quickstart.