Skip to main content

​
Quickstart

Follow this streamlined path to get value quickly while keeping production-safe defaults.
1

Install and authenticate

cerulion --version
cerulion auth login --browser
Authentication persists in ~/.config/cerulion/credentials. Use --token for headless CI.
2

Initialize a project

mkdir telemetry-hub && cd telemetry-hub
cerulion init --template minimal
The initializer scaffolds a schema folder, sample nodes, and a .cerulion/config.yaml with sane defaults.
3

Configure your profile

cerulion profile use staging
cerulion config set transport.local iceoryx2
cerulion config set transport.network zenoh
Profiles keep credentials, transports, and environment targets isolated per stage.
4

Validate schemas

cerulion validate schema ./schemas
Exit code 0 means the schema is compatible with Cerulion Core and language generators.
5

Run locally

cerulion run local --watch
Hot reloads nodes on file changes and streams logs inline. Press q to gracefully stop.
6

Build and publish a bundle

cerulion build --output dist/telemetry-hub.cerbundle
cerulion bundle publish dist/telemetry-hub.cerbundle --env staging
Builds are content-addressed and signed. Publishing promotes the bundle to the selected environment.

​
What you just accomplished

  • Created a typed schema validated against Cerulion Core
  • Ran a local graph with zero-copy transports enabled
  • Produced a signed bundle and promoted it to a remote environment

​
Next steps

  • Explore the full command reference to customize the build and deploy process.
  • Automate the flow in CI using cerulion auth login --token and cerulion bundle publish --dry-run for gated releases.
  • Add observability with cerulion logs and cerulion metrics once your bundle is live.