Appearance
nkapp run
Deprecated — use nkapp up
Since the up/deploy split, the default nkapp up is the old run: a service-only reconcile with no infrastructure plan/apply and no remote code sync. nkapp run now prints a deprecation notice and delegates to the exact same code path. Use nkapp up.
bash
nkapp run [service] [options]Options
| Flag | Type | Default | Description |
|---|---|---|---|
-e, --env <env> | string | local | Target environment |
-b, --branch <name> | string | — | Explicitly work with a database branch (isolate data) |
The positional [service] accepts a service name or a database name — nkapp run my_db reconciles just that database instance.
Exact behavior
run calls the same action as up, with three values pinned:
- One-shot — tunnels are closed and the process exits after orchestration (equivalent to
up --detach). This preserves the historicalrunbehavior. - Never provisions — the infrastructure phase is pinned off. Not even
NANOKIT_UP_LEGACY=1can re-enable it here. - Never syncs — the remote code sync is pinned off for the same reason.
It therefore has no --infra, --sync or --legacy flags: there is nothing for them to turn on.
Migration
| You used to run | Run this instead |
|---|---|
nkapp run | nkapp up --detach |
nkapp run api -e stage | nkapp up api -e stage --detach |
nkapp up (expecting infra + sync) | nkapp deploy, or nkapp up --legacy |