greentic-start 0.4.4

Greentic lifecycle runner for start/restart/stop orchestration
docs.rs failed to build greentic-start-0.4.4
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.
Visit the last successful build: greentic-start-0.4.13

greentic-start

greentic-start is the lifecycle runner for Greentic demo/app-pack execution. It exposes lifecycle orchestration as a library (greentic_start::run_from_env) and a thin CLI binary.

Ownership

  • greentic-start owns lifecycle execution (start/up/stop/restart).
  • greentic-operator (including Wizard) owns UX and planning, then delegates lifecycle execution to greentic-start.
  • Details: docs/ownership.md.

CLI Surface

Primary commands:

  • greentic-start start
  • greentic-start restart
  • greentic-start stop

Primary runtime inputs:

  • --config <path> to point at the demo config
  • --tenant <name>
  • --team <name>
  • --nats, --cloudflared, --ngrok
  • --log-dir, --verbose, --quiet

Extension pack roles

  • Core platform packs: runtime-critical packs such as messaging, events, oauth, telemetry, secrets, and state integrations.
  • Optional extension packs: packs exposing hooks, contracts, capabilities, subscriptions, or other feature extensions for app packs/components.

greentic-start now classifies these roles explicitly so lifecycle boot can reason about platform services separately from optional extensions.

i18n

  • Source catalog: i18n/en.json.
  • Translator helper: tools/i18n.sh (defaults to LANGS=all, BATCH_SIZE=200).

CI and Releases

Local validation:

bash ci/local_check.sh

Release flow:

  1. Bump version in Cargo.toml.
  2. Create and push tag vX.Y.Z (must match Cargo.toml).
  3. Push tag to trigger .github/workflows/publish.yml.

Required secrets:

  • CARGO_REGISTRY_TOKEN for crates.io publish.

Security

See SECURITY.md for vulnerability reporting and supported version policy.