> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kombify.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Legacy and deprecated commands

> Commands current releases refuse or replace

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.

<Warning>Current releases refuse this command; it belongs to the exact v0.6 compatibility line.</Warning>

```bash theme={null}
stackkit app add <name> [flags]
```

| Flag            | Type        | Default         | Description                                                                   |
| --------------- | ----------- | --------------- | ----------------------------------------------------------------------------- |
| `--auth`        | string      | `login-gateway` | Route auth mode: login-gateway or public                                      |
| `--env`         | stringArray | —               | Plain environment variable as KEY=value; repeatable                           |
| `--health-path` | string      | `/health`       | HTTP health path                                                              |
| `--host`        | string      | —               | Route host for the app                                                        |
| `--image`       | string      | —               | Container image for the PaaS handoff                                          |
| `--kind`        | string      | `sveltekit`     | App kind (currently only sveltekit)                                           |
| `--port`        | int         | `3000`          | Container port exposed by the app                                             |
| `--secret`      | stringArray | —               | Secret reference as KEY=env:NAME, KEY=vault:NAME or KEY=file:PATH; repeatable |

## stackkit backup list

List snapshots in the local repository.

<Warning>Current releases refuse this command; it belongs to the exact v0.6 compatibility line.</Warning>

```bash theme={null}
stackkit backup list [flags]
```

| Flag     | Type | Default | Description              |
| -------- | ---- | ------- | ------------------------ |
| `--json` | bool | —       | Output snapshots as JSON |

## stackkit backup migrate-from-restic

Import an existing Restic repository into Kopia (one-shot).

<Warning>Current releases refuse this command; it belongs to the exact v0.6 compatibility line.</Warning>

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.

```bash theme={null}
stackkit backup migrate-from-restic [flags]
```

| Flag        | Type | Default | Description                      |
| ----------- | ---- | ------- | -------------------------------- |
| `--dry-run` | bool | —       | Print the plan without importing |

## stackkit backup verify

Validate the repository against its storage provider.

<Warning>Current releases refuse this command; it belongs to the exact v0.6 compatibility line.</Warning>

```bash theme={null}
stackkit backup verify [flags]
```

## stackkit cluster join-token

Create a join token for worker or storage nodes.

<Warning>Current releases refuse this command; it belongs to the exact v0.6 compatibility line.</Warning>

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.

```bash theme={null}
stackkit cluster join-token [flags]
```

| Flag           | Type     | Default                             | Description                                                      |
| -------------- | -------- | ----------------------------------- | ---------------------------------------------------------------- |
| `--endpoint`   | string   | —                                   | Main node endpoint workers use to join                           |
| `--homelab-id` | string   | —                                   | Homelab ID (defaults to stack spec name)                         |
| `--main-node`  | string   | —                                   | Main node ID/name (defaults to the main-like node in stack spec) |
| `--output, -o` | string   | `.stackkit/cluster/join-token.json` | Output path for the token JSON                                   |
| `--ttl`        | duration | `24h0m0s`                           | Token validity duration                                          |

## stackkit kit upgrade

Resolve and install a verified StackKit release.

<Warning>Deprecated: use stackkit upgrade</Warning>

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.

```bash theme={null}
stackkit kit upgrade [flags]
```

| Flag        | Type   | Default  | Description                                                                             |
| ----------- | ------ | -------- | --------------------------------------------------------------------------------------- |
| `--dry-run` | bool   | —        | Verify and inspect target generation in a bounded shadow workspace without applying it. |
| `--json`    | bool   | —        | Emit stackkit.command-result/v1 JSON.                                                   |
| `--recover` | string | —        | Explicitly recover one exact interrupted lifecycle operation ID.                        |
| `--to`      | string | `latest` | Target: latest, vX.Y.Z, or channel:stable\|beta\|edge.                                  |

**Examples**

```bash theme={null}
# Verify the newest stable release and preview its plan and artifact diff without applying it
stackkit upgrade --dry-run

# Upgrade to the newest stable release
stackkit upgrade

# Upgrade to the newest beta prerelease
stackkit upgrade --to channel:beta

# Recover an interrupted upgrade by its lifecycle operation ID
stackkit upgrade --recover <operation-id>
```

## stackkit kit verify

Verify cached release receipts and attestations.

<Warning>Deprecated: use stackkit verify `--offline`</Warning>

Deprecated alias for 'stackkit verify `--offline`'. No network request is performed.

```bash theme={null}
stackkit kit verify [flags]
```

| Flag     | Type | Default | Description                           |
| -------- | ---- | ------- | ------------------------------------- |
| `--json` | bool | —       | Emit stackkit.command-result/v1 JSON. |

## stackkit status

Show deployment status.

<Warning>Current releases refuse this command; it belongs to the exact v0.6 compatibility line.</Warning>

Display the current status of the StackKit deployment.

```text theme={null}
Shows:
  • Deployment state (running, degraded, error)
  • Service statuses and health
  • Resource usage
  • URLs and endpoints
```

```bash theme={null}
stackkit status [flags]
```

| Flag              | Type   | Default | Description                                                                               |
| ----------------- | ------ | ------- | ----------------------------------------------------------------------------------------- |
| `--http`          | bool   | —       | Probe verified service routes from this verifier host                                     |
| `--inventory`     | string | —       | Architecture v2 observed Inventory used to identify a configured Standard process runtime |
| `--json`          | bool   | —       | Output as JSON                                                                            |
| `--resolved-plan` | string | —       | Canonical Architecture v2 ResolvedPlan (default: deploy/.stackkit/resolved-plan.json)     |

**Examples**

```bash theme={null}
# Show status
stackkit status

# Output as JSON
stackkit status --json
```