Getting Started
Section titled “Getting Started”This guide assumes capsule-cli v0.3 and LIFECYCLE_SPEC v1.2,
showing the shortest path to create and run a new Capsule.
Prerequisites
Section titled “Prerequisites”capsulecommand available- Local working directory with write access
- For signing: write access to
~/.capsule/keys
capsule --helpcapsule engine featuresEngine Setup
Section titled “Engine Setup”The standard procedure for Source runtime is capsule setup --engine nacelle. For existing binaries, use capsule engine register.
capsule setup --engine nacellecapsule engine register --name nacelle --path /usr/local/bin/nacelle --defaultCreate a New Capsule
Section titled “Create a New Capsule”Use capsule new for template generation. Available templates: python|node|hono|rust|go|shell.
capsule new hello-capsule --template nodecd hello-capsuleMinimal capsule.toml (Lifecycle shortcut) example:
schema_version = "1.1"name = "hello-capsule"version = "0.1.0"type = "app"
[lifecycle]run = "node index.js"port = 3000health_check = "/health"Validate and Run
Section titled “Validate and Run”- Validate manifest -
capsule validate .checks syntax/semantics/IPC conflicts. - Run capsule -
capsule open .executes thecapsule.toml. - Monitor process -
capsule ps/capsule logs/capsule closefor management.
capsule validate .capsule open . --watchcapsule ps --allcapsule logs --name hello-capsule --followPack and Sign
Section titled “Pack and Sign”For distribution, create a .capsule and sign with Ed25519 key. Signed artifacts can be reused in public flows or CI.
capsule pack . --initcapsule keygen --out ~/.capsule/keys/default.pemcapsule sign ./dist/hello-capsule.capsule --key ~/.capsule/keys/default.pemNext Steps
Section titled “Next Steps”- For manifest and lifecycle details, see Core Concepts
- For command options, see CLI Reference
- For Store publication, see Publish Guideline
Source specs: CAPSULE_CLI_SPEC v0.3, DRAFT_LIFECYCLE v1.2.