Skip to main content
These commands exist in the command tree but are not part of the current workflow. Legacy commands are refused on current releases; deprecated commands still run and name their replacement.

​
stackkit app add

Add or update a v0.6 compatibility PaaS app handoff.
Current releases refuse this command; it belongs to the exact v0.6 compatibility line.

​
stackkit backup list

List snapshots in the local repository.
Current releases refuse this command; it belongs to the exact v0.6 compatibility line.

​
stackkit backup migrate-from-restic

Import an existing Restic repository into Kopia (one-shot).
Current releases refuse this command; it belongs to the exact v0.6 compatibility line.
Drive the one-shot Restic-to-Kopia importer. Reads the Restic repository configured in the v1 addon, walks every snapshot, and re-creates it inside Kopia preserving original timestamps. After a successful import the addon flips engine: “restic-import” to “kopia” automatically.

​
stackkit backup verify

Validate the repository against its storage provider.
Current releases refuse this command; it belongs to the exact v0.6 compatibility line.

​
stackkit cluster join-token

Create a join token for worker or storage nodes.
Current releases refuse this command; it belongs to the exact v0.6 compatibility line.
Create a join token for worker or storage nodes. The token is the only supported path for treating another BaseKit install as a member of this homelab. Coolify remote-server registration and TechStack mirror updates consume this cluster identity in later rollout steps.

​
stackkit kit upgrade

Resolve and install a verified StackKit release.
Deprecated: use stackkit upgrade
Resolve a public StackKit release from GitHub, verify its archive, SPDX SBOM, GitHub OIDC/Sigstore attestation, and cached trusted root, then atomically install it under .stackkit/releases/. With --dry-run it generates the verified target only in a bounded shadow workspace and reports a canonical plan/artifact diff. Without --dry-run it first inspects that target, creates a native Kopia snapshot plus an owner-signed executor-state recovery checkpoint, stages and verifies the rollback data without activating it, and only then installs and executes the exact target generate/apply/verify transaction. A failed target transaction can restore and verify the prior executor only before target Apply is admitted. After Apply, prior-runtime restart is blocked until verified prior-data activation exists; isolated Kopia staging alone does not authorize it. A completed target commit keeps its success proof for explicit finalization. Fresh upgrades require support in the embedded CUE Kit policy; recovery of an existing operation follows its signed journal and checkpoint.
Examples

​
stackkit kit verify

Verify cached release receipts and attestations.
Deprecated: use stackkit verify --offline
Deprecated alias for ‘stackkit verify --offline’. No network request is performed.

​
stackkit status

Show deployment status.
Current releases refuse this command; it belongs to the exact v0.6 compatibility line.
Display the current status of the StackKit deployment.
Examples