@nocobase/cli 2.1.0-alpha.25 → 2.1.0-alpha.27

package/README.md

@@ -60,12 +60,16 @@ nb init --ui
 When creating a new app, it can also install NocoBase AI coding skills
 (`nocobase/skills`) globally.
 
+Use `--skip-skills` if the skills are managed separately, or when running in CI
+or offline environments where `nb init` should not install or update them.
+
 ### Non-Interactive Setup
 
 When prompts are skipped, an app/env name is required:
 
 ```bash
 nb init --env app1 --yes
+nb init --env app1 --yes --skip-skills
 ```
 
 Install with Docker:
@@ -111,17 +115,12 @@ If `nb init` was interrupted after the env config had already been saved, you ca
 
 ```bash
 nb init --env app1 --resume
-```
-
-The advanced low-level equivalent is:
-
-```bash
-nb install --env app1 --resume
+nb init --env app1 --resume --skip-skills
 ```
 
 `--resume` reuses the saved workspace env config for app, source, database, and env connection settings. In interactive mode, it only asks for any missing setup-only values.
 
-In non-interactive mode, pass these setup-only flags again because they are not saved in env config:
+In non-interactive resume mode, `nb init --resume --yes` uses default initialization values unless these flags are passed explicitly:
 
 - `--lang`
 - `--root-username`
@@ -134,40 +133,32 @@ In non-interactive mode, pass these setup-only flags again because they are not
 | Command | Description |
 | --- | --- |
 | `nb init` | Set up NocoBase and connect it as a CLI env for coding agents. |
-| `nb install` | Advanced command used by `nb init` to install a local NocoBase app and save env config. In most cases, use `nb init` instead. |
-| `nb download` | Advanced command used by `nb init` or `nb upgrade` to fetch NocoBase from Docker, npm, or Git. It is rarely used directly. |
-| `nb start` | Start the selected local app or Docker container. |
-| `nb stop` | Stop the selected local app or Docker container. |
-| `nb restart` | Stop, then start the selected local app or Docker container. |
-| `nb dev` | Run development mode for npm/Git source envs. |
-| `nb logs` | Show app logs for npm/Git or Docker envs. |
-| `nb ps` | Show runtime status for configured envs. |
+| `nb app` | Manage app runtimes: start, stop, restart, logs, cleanup, and upgrades. |
+| `nb source` | Manage the local source project: download, develop, build, and test. |
 | `nb db` | Inspect or manage built-in database runtime status for local envs. |
-| `nb upgrade` | Refresh code/image and restart the selected app. |
-| `nb down` | Stop and remove local runtime containers for an env. |
 | `nb env` | Manage saved CLI env connections. |
 | `nb api` | Call NocoBase API resources from the CLI. |
-| `nb pm` | Manage plugins for the selected NocoBase env. |
+| `nb plugin` | Manage plugins for the selected NocoBase env. |
 | `nb self` | Check or update the installed NocoBase CLI. |
 | `nb skills` | Check, install, or update global NocoBase AI coding skills. |
 
-Recommended style: use `--env` explicitly for app/runtime commands. `-e` is the short form:
+Recommended style: pass the env name explicitly when operating on a specific env. Runtime commands accept `--env`, and `nb env info` also accepts a positional env name:
 
 ```bash
-nb start --env app1
-nb restart --env app1
-nb logs --env app1
-nb ps --env app1
+nb app start --env app1
+nb app restart --env app1
+nb app logs --env app1
+nb env info app1
 nb db ps --env app1
 ```
 
 Equivalent shorthand examples:
 
 ```bash
-nb start -e app1
-nb restart -e app1
-nb logs -e app1
-nb upgrade -e app1
+nb app start -e app1
+nb app restart -e app1
+nb app logs -e app1
+nb app upgrade -e app1
 nb db start -e app1
 ```
 
@@ -208,18 +199,18 @@ Docker envs are managed through saved Docker containers and images:
 
 ```bash
 nb init --env app1 --yes --source docker --version alpha
-nb start --env app1
-nb restart --env app1
-nb logs --env app1
-nb stop --env app1
+nb app start --env app1
+nb app restart --env app1
+nb app logs --env app1
+nb app stop --env app1
 ```
 
 Docker downloads support platform selection:
 
 ```bash
-nb download --source docker --version alpha --docker-platform auto
-nb download --source docker --version alpha --docker-platform linux/amd64
-nb download --source docker --version alpha --docker-platform linux/arm64
+nb source download --source docker --version alpha --docker-platform auto
+nb source download --source docker --version alpha --docker-platform linux/amd64
+nb source download --source docker --version alpha --docker-platform linux/arm64
 ```
 
 ### npm and Git
@@ -228,11 +219,11 @@ npm and Git envs use a local source directory and can run development mode:
 
 ```bash
 nb init --env app1 --yes --source git --version alpha
-nb dev --env app1
+nb source dev --env app1
 ```
 
-`nb dev` only supports npm/Git source envs. Docker envs can be inspected with
-`nb logs`, and remote envs only support API/env operations.
+`nb source dev` only supports npm/Git source envs. Docker envs can be inspected with
+`nb app logs`, and remote envs only support API/env operations.
 
 ### Existing NocoBase App
 
@@ -250,14 +241,14 @@ nb env add app1 --api-base-url http://localhost:13000/api
 Upgrade refreshes the saved source or image, then restarts the app:
 
 ```bash
-nb upgrade --env app1
+nb app upgrade --env app1
 ```
 
 Use `--skip-code-update` or `-s` to restart with the saved local code or Docker
 image without downloading updates first:
 
 ```bash
-nb upgrade --env app1 -s
+nb app upgrade --env app1 -s
 ```
 
 ## Database Commands
@@ -283,23 +274,19 @@ Notes:
 Bring down a local env:
 
 ```bash
-nb down --env app1
+nb app down --env app1
 ```
 
-By default, `nb down` stops the app and removes app/database containers if they
-exist. It keeps user data, source files, and CLI env config.
+By default, `nb app down` stops the app and removes app/database containers if they
+exist. For local envs, it also deletes the saved local app files. It keeps storage data and CLI env config.
 
 Use explicit flags for destructive cleanup:
 
 ```bash
-nb down --env app1 --remove-data
-nb down --env app1 --remove-source
-nb down --env app1 --remove-env
+nb app down --env app1 --all --yes
 ```
 
-- `--remove-data`: delete storage and managed database data. This requires confirmation unless `--yes` is used.
-- `--remove-source`: delete the npm/Git source directory.
-- `--remove-env`: remove the saved CLI env config.
+- `--all`: delete everything for the env, including storage data and the saved env config. This requires `--yes`.
 
 ## Environment Management
 
@@ -309,12 +296,18 @@ Show the current env:
 nb env
 ```
 
-List configured envs:
+List configured envs with token-verified API status:
 
 ```bash
 nb env list
 ```
 
+Show details for one env:
+
+```bash
+nb env info app1
+```
+
 Switch the current env:
 
 ```bash
@@ -343,6 +336,23 @@ nb api resource get --resource users --filter-by-tk 1 -e app1
 nb api resource create --resource users --values '{"nickname":"Ada"}' -e app1
 ```
 
+Create and download a backup:
+
+```bash
+nb api backup create -e app1
+nb api backup status --name backup_20260430_120000_1234.nbdata -e app1
+nb api backup download --name backup_20260430_120000_1234.nbdata --output ./backup.nbdata -e app1
+```
+
+Restore or run a migration package:
+
+```bash
+nb api backup restore-upload --file ./backup.nbdata -e app1
+nb api migration rules create --name default --user-defined-rule schema-only --system-defined-rule overwrite-first -e app1
+nb api migration create --rule-id 1 --title release-20260430 -e app1
+nb api migration execute --file ./migration.nbdata -e app1
+```
+
 Use `-j, --json-output` to print raw JSON when available:
 
 ```bash
@@ -357,9 +367,11 @@ Available API command topics:
 | `nb api api-keys` | Manage API keys for HTTP API access. |
 | `nb api app` | Manage application resources. |
 | `nb api authenticators` | Manage user authentication, including password auth, SMS auth, SSO protocols, and extensible providers. |
+| `nb api backup` | Create, download, remove, and restore backups. |
 | `nb api data-modeling` | Manage data sources, collections, and database modeling resources. |
 | `nb api file-manager` | Manage file storage services, file collections, and attachment fields. |
 | `nb api flow-surfaces` | Compose and mutate page, tab, block, field, and action surfaces. |
+| `nb api migration` | Create, check, execute, and inspect migration packages. |
 | `nb api pm` | Manage plugins through API commands. |
 | `nb api resource` | Work with generic collection resources. |
 | `nb api system-settings` | Adjust system title, logo, language, and other global settings. |

package/README.zh-CN.md

@@ -55,12 +55,15 @@ nb init --ui
 
 `nb init` 可以连接已有的 NocoBase 应用，也可以安装一个新的 NocoBase 应用。创建新应用时，还可以全局安装 NocoBase AI coding skills (`nocobase/skills`)。
 
+如果已经自行管理 skills，或在 CI、离线环境中运行，不希望 `nb init` 安装或更新 skills，可以传入 `--skip-skills`。
+
 ### 非交互式初始化
 
 跳过交互提示时，必须提供 app/env name：
 
 ```bash
 nb init --env app1 --yes
+nb init --env app1 --yes --skip-skills
 ```
 
 使用 Docker 安装：
@@ -106,17 +109,12 @@ nb init --env app1 --yes --source git --version fix/cli-v2
 
 ```bash
 nb init --env app1 --resume
-```
-
-对应的底层高级命令是：
-
-```bash
-nb install --env app1 --resume
+nb init --env app1 --resume --skip-skills
 ```
 
 `--resume` 会复用工作区里已保存的 env config，包括应用、source、数据库和 env 连接相关配置。在交互模式下，只会继续补齐缺失的初始化参数。
 
-在非交互模式下，需要重新传这些只用于初始化、不会保存到 env config 的参数：
+在非交互恢复模式下，如果没有显式传入这些参数，`nb init --resume --yes` 会使用默认初始化值：
 
 - `--lang`
 - `--root-username`
@@ -129,38 +127,30 @@ nb install --env app1 --resume
 | 命令 | 说明 |
 | --- | --- |
 | `nb init` | 初始化 NocoBase，并连接为 coding agent 可使用的 CLI env。 |
-| `nb install` | `nb init` 内部会使用的高级命令，用于安装本地 NocoBase 应用并保存 env 配置。通常建议直接使用 `nb init`。 |
-| `nb download` | `nb init` 或 `nb upgrade` 会使用的高级命令，用于从 Docker、npm 或 Git 获取 NocoBase。通常很少直接使用。 |
-| `nb start` | 启动选中的本地应用或 Docker 容器。 |
-| `nb stop` | 停止选中的本地应用或 Docker 容器。 |
-| `nb restart` | 先停止，再启动选中的本地应用或 Docker 容器。 |
-| `nb dev` | 为 npm/Git 源码 env 启动开发模式。 |
-| `nb logs` | 查看 npm/Git 或 Docker env 的应用日志。 |
-| `nb ps` | 查看已配置 env 的运行状态。 |
+| `nb app` | 管理应用运行态：启动、停止、重启、日志、状态、清理和升级。 |
+| `nb source` | 管理本地源码工程：下载、开发、构建和测试。 |
 | `nb db` | 查看或管理本地 env 的内置数据库运行状态。 |
-| `nb upgrade` | 更新源码/镜像并重启选中的应用。 |
-| `nb down` | 停止并移除某个 env 的本地运行容器。 |
 | `nb env` | 管理已保存的 CLI env 连接。 |
 | `nb api` | 通过 CLI 调用 NocoBase API 资源。 |
-| `nb pm` | 管理选中 NocoBase env 的插件。 |
+| `nb plugin` | 管理选中 NocoBase env 的插件。 |
 
-推荐在应用和运行时相关命令里显式使用 `--env`；`-e` 是它的简写：
+推荐在操作指定 env 时显式传入 env 名称。运行时命令支持 `--env`，`nb env info` 也支持位置参数：
 
 ```bash
-nb start --env app1
-nb restart --env app1
-nb logs --env app1
-nb ps --env app1
+nb app start --env app1
+nb app restart --env app1
+nb app logs --env app1
+nb env info app1
 nb db ps --env app1
 ```
 
 等价的简写示例：
 
 ```bash
-nb start -e app1
-nb restart -e app1
-nb logs -e app1
-nb upgrade -e app1
+nb app start -e app1
+nb app restart -e app1
+nb app logs -e app1
+nb app upgrade -e app1
 nb db start -e app1
 ```
 
@@ -172,18 +162,18 @@ Docker env 会通过已保存的 Docker 容器和镜像进行管理：
 
 ```bash
 nb init --env app1 --yes --source docker --version alpha
-nb start --env app1
-nb restart --env app1
-nb logs --env app1
-nb stop --env app1
+nb app start --env app1
+nb app restart --env app1
+nb app logs --env app1
+nb app stop --env app1
 ```
 
 Docker 下载支持指定平台：
 
 ```bash
-nb download --source docker --version alpha --docker-platform auto
-nb download --source docker --version alpha --docker-platform linux/amd64
-nb download --source docker --version alpha --docker-platform linux/arm64
+nb source download --source docker --version alpha --docker-platform auto
+nb source download --source docker --version alpha --docker-platform linux/amd64
+nb source download --source docker --version alpha --docker-platform linux/arm64
 ```
 
 ### npm 和 Git
@@ -192,10 +182,10 @@ npm 和 Git env 会使用本地源码目录，并支持开发模式：
 
 ```bash
 nb init --env app1 --yes --source git --version alpha
-nb dev --env app1
+nb source dev --env app1
 ```
 
-`nb dev` 只支持 npm/Git 源码 env。Docker env 可以通过 `nb logs` 查看日志，remote env 只支持 API 和 env 相关操作。
+`nb source dev` 只支持 npm/Git 源码 env。Docker env 可以通过 `nb app logs` 查看日志，remote env 只支持 API 和 env 相关操作。
 
 ### 已有 NocoBase 应用
 
@@ -212,13 +202,13 @@ nb env add app1 --api-base-url http://localhost:13000/api
 升级会更新已保存的源码或镜像，然后重启应用：
 
 ```bash
-nb upgrade --env app1
+nb app upgrade --env app1
 ```
 
 如果只想使用当前已保存的本地源码或 Docker 镜像重启应用，可以使用 `--skip-code-update` 或 `-s`：
 
 ```bash
-nb upgrade --env app1 -s
+nb app upgrade --env app1 -s
 ```
 
 ## 数据库命令
@@ -244,22 +234,19 @@ nb db logs --env app1
 关闭并清理某个本地 env：
 
 ```bash
-nb down --env app1
+nb app down --env app1
 ```
 
-默认情况下，`nb down` 会停止应用，并在存在时移除应用容器和数据库容器。它不会删除用户数据、源码文件和 CLI env 配置。
+默认情况下，`nb app down` 会停止应用，并在存在时移除应用容器和数据库容器。它不会删除用户数据、源码文件和 CLI env 配置。
+对于本地 env，它还会删除已保存的本地 app 目录。默认仍会保留 storage 数据和 CLI env 配置。
 
 如需执行破坏性清理，需要显式指定参数：
 
 ```bash
-nb down --env app1 --remove-data
-nb down --env app1 --remove-source
-nb down --env app1 --remove-env
+nb app down --env app1 --all --yes
 ```
 
-- `--remove-data`：删除 storage 和托管数据库数据。除非使用 `--yes`，否则需要二次确认。
-- `--remove-source`：删除 npm/Git 源码目录。
-- `--remove-env`：删除已保存的 CLI env 配置。
+- `--all`：删除该 env 的所有内容，包括 storage 数据和已保存的 CLI env 配置。必须同时传 `--yes`。
 
 ## Env 管理
 
@@ -269,12 +256,18 @@ nb down --env app1 --remove-env
 nb env
 ```
 
-查看已配置的 env：
+查看已配置的 env 及 Token 验证后的 API 状态：
 
 ```bash
 nb env list
 ```
 
+查看某个 env 的详情：
+
+```bash
+nb env info app1
+```
+
 切换当前 env：
 
 ```bash

package/dist/commands/app/down.js

@@ -0,0 +1,259 @@
+/**
+ * This file is part of the NocoBase (R) project.
+ * Copyright (c) 2020-2024 NocoBase Co., Ltd.
+ * Authors: NocoBase Team.
+ *
+ * This project is dual-licensed under AGPL-3.0 and NocoBase Commercial License.
+ * For more information, please refer to: https://www.nocobase.com/agreement.
+ */
+import * as p from '@clack/prompts';
+import { Command, Flags } from '@oclif/core';
+import fsp from 'node:fs/promises';
+import os from 'node:os';
+import path from 'node:path';
+import { buildDockerDbContainerName, formatMissingManagedAppEnvMessage, resolveManagedAppRuntime, runLocalNocoBaseCommand, } from '../../lib/app-runtime.js';
+import { removeEnv } from '../../lib/auth-store.js';
+import { resolveConfiguredEnvPath } from '../../lib/cli-home.js';
+import { commandOutput, commandSucceeds, run } from '../../lib/run-npm.js';
+import { failTask, isInteractiveTerminal, printInfo, startTask, succeedTask, } from '../../lib/ui.js';
+function resolveConfiguredPath(value) {
+    return resolveConfiguredEnvPath(value);
+}
+function assertSafeRemovalPath(target, label) {
+    const resolved = path.resolve(target);
+    const cwd = path.resolve(process.cwd());
+    const home = path.resolve(os.homedir());
+    const root = path.parse(resolved).root;
+    if (resolved === root || resolved === cwd || resolved === home) {
+        throw new Error(`Refusing to remove ${label} at "${resolved}" because it is too broad.`);
+    }
+}
+async function removePathIfExists(target, label) {
+    const resolved = path.resolve(target);
+    assertSafeRemovalPath(resolved, label);
+    await fsp.rm(resolved, { recursive: true, force: true });
+}
+async function dockerContainerExists(containerName) {
+    return await commandSucceeds('docker', ['container', 'inspect', containerName]);
+}
+async function removeDockerContainerIfExists(containerName) {
+    if (!(await dockerContainerExists(containerName))) {
+        return 'missing';
+    }
+    await run('docker', ['rm', '-f', containerName], {
+        errorName: 'docker rm',
+        stdio: 'ignore',
+    });
+    return 'removed';
+}
+async function dockerNetworkExists(networkName) {
+    return await commandSucceeds('docker', ['network', 'inspect', networkName]);
+}
+async function dockerNetworkHasActiveEndpoints(networkName) {
+    try {
+        const output = await commandOutput('docker', [
+            'network',
+            'inspect',
+            networkName,
+            '--format',
+            '{{json .Containers}}',
+        ], {
+            errorName: 'docker network inspect',
+        });
+        const containers = JSON.parse(output || '{}');
+        return Boolean(containers && typeof containers === 'object' && Object.keys(containers).length > 0);
+    }
+    catch {
+        return false;
+    }
+}
+async function removeDockerNetworkIfUnused(networkName) {
+    if (!(await dockerNetworkExists(networkName))) {
+        return 'missing';
+    }
+    try {
+        await run('docker', ['network', 'rm', networkName], {
+            errorName: 'docker network rm',
+            stdio: 'ignore',
+        });
+        return 'removed';
+    }
+    catch (error) {
+        const message = error instanceof Error ? error.message : String(error);
+        if (/has active endpoints|is in use|active endpoints/i.test(message)
+            || (await dockerNetworkExists(networkName) && await dockerNetworkHasActiveEndpoints(networkName))) {
+            return 'in-use';
+        }
+        throw error;
+    }
+}
+function builtinDbContainerName(runtime) {
+    if (!runtime.env.config.builtinDb) {
+        return undefined;
+    }
+    const dbDialect = String(runtime.env.config.dbDialect ?? 'postgres').trim() || 'postgres';
+    return buildDockerDbContainerName(runtime.envName, dbDialect, runtime.dockerContainerPrefix || runtime.workspaceName);
+}
+function managedDockerNetworkName(runtime) {
+    return runtime.dockerNetworkName?.trim() || runtime.workspaceName?.trim() || undefined;
+}
+async function confirmDownAll(envName, yes) {
+    if (yes) {
+        return true;
+    }
+    if (!isInteractiveTerminal()) {
+        throw new Error(`\`nb app down --all\` needs confirmation. Re-run with --yes to delete everything for "${envName}" in non-interactive mode.`);
+    }
+    const answer = await p.confirm({
+        message: `Delete everything for "${envName}"? This removes the app, managed containers, storage data, and the saved CLI env config.`,
+        active: 'yes',
+        inactive: 'no',
+        initialValue: false,
+    });
+    if (p.isCancel(answer)) {
+        p.cancel('Down cancelled.');
+        return false;
+    }
+    return answer;
+}
+function formatDownFailure(envName, message) {
+    return [
+        `Couldn't bring down NocoBase for "${envName}".`,
+        'Some local runtime resources may still exist. Check Docker or the local app process, then try again.',
+        `Details: ${message}`,
+    ].join('\n');
+}
+export default class AppDown extends Command {
+    static hidden = false;
+    static description = 'Bring down the selected env by removing runtime containers and the saved local app files. Storage data and env config are kept unless explicitly requested.';
+    static examples = [
+        '<%= config.bin %> <%= command.id %> --env app1',
+        '<%= config.bin %> <%= command.id %> --env app1 --all --yes',
+    ];
+    static flags = {
+        env: Flags.string({
+            char: 'e',
+            description: 'CLI env name to bring down. Defaults to the current env when omitted',
+        }),
+        all: Flags.boolean({
+            description: 'Delete everything for this env, including storage data and the saved env config',
+            default: false,
+        }),
+        yes: Flags.boolean({
+            char: 'y',
+            description: 'Confirm destructive actions without prompting',
+            default: false,
+        }),
+        verbose: Flags.boolean({
+            description: 'Show raw output from shutdown commands',
+            default: false,
+        }),
+    };
+    async run() {
+        const { flags } = await this.parse(AppDown);
+        const requestedEnv = flags.env?.trim() || undefined;
+        const removeData = Boolean(flags.all);
+        const removeEnvConfig = Boolean(flags.all);
+        const runtime = await resolveManagedAppRuntime(requestedEnv);
+        if (!runtime) {
+            this.error(formatMissingManagedAppEnvMessage(requestedEnv));
+        }
+        if (runtime.kind === 'http') {
+            this.error([
+                `Can't bring down "${runtime.envName}" from this machine.`,
+                'This env only has an API connection, so there is no saved local app, Docker app, or managed database to remove here.',
+                'Use `nb env remove` if you only want to remove the CLI connection config.',
+            ].join('\n'));
+        }
+        if (runtime.kind === 'ssh') {
+            this.error([
+                `Can't bring down "${runtime.envName}" yet.`,
+                'SSH env support is reserved but not implemented yet.',
+                'Use `nb env remove` if you only want to remove the saved CLI config for now.',
+            ].join('\n'));
+        }
+        if (flags.all) {
+            let confirmed = false;
+            try {
+                confirmed = await confirmDownAll(runtime.envName, flags.yes);
+            }
+            catch (error) {
+                this.error(error instanceof Error ? error.message : String(error));
+            }
+            if (!confirmed) {
+                return;
+            }
+        }
+        try {
+            if (runtime.kind === 'docker') {
+                startTask(`Removing Docker app container for "${runtime.envName}"...`);
+                const state = await removeDockerContainerIfExists(runtime.containerName);
+                succeedTask(state === 'removed'
+                    ? `Docker app container removed for "${runtime.envName}".`
+                    : `No Docker app container found for "${runtime.envName}".`);
+            }
+            else {
+                startTask(`Stopping local NocoBase app for "${runtime.envName}"...`);
+                await runLocalNocoBaseCommand(runtime, ['pm2', 'kill'], {
+                    stdio: flags.verbose ? 'inherit' : 'ignore',
+                });
+                succeedTask(`Local NocoBase app stopped for "${runtime.envName}".`);
+            }
+            if (runtime.kind === 'local' || runtime.kind === 'docker') {
+                const dbContainerName = builtinDbContainerName(runtime);
+                if (dbContainerName) {
+                    startTask(`Removing built-in database container for "${runtime.envName}"...`);
+                    const state = await removeDockerContainerIfExists(dbContainerName);
+                    succeedTask(state === 'removed'
+                        ? `Built-in database container removed for "${runtime.envName}".`
+                        : `No built-in database container found for "${runtime.envName}".`);
+                }
+                const networkName = managedDockerNetworkName(runtime);
+                if (networkName) {
+                    startTask(`Removing Docker network for "${runtime.envName}" if unused...`);
+                    const state = await removeDockerNetworkIfUnused(networkName);
+                    if (state === 'removed') {
+                        succeedTask(`Docker network removed for "${runtime.envName}".`);
+                    }
+                    else if (state === 'missing') {
+                        succeedTask(`No Docker network found for "${runtime.envName}".`);
+                    }
+                    else {
+                        succeedTask(`Docker network is still in use for "${runtime.envName}". Keeping it.`);
+                    }
+                }
+            }
+            if (runtime.kind === 'local') {
+                const localAppPath = resolveConfiguredPath(runtime.env.config.appRootPath) || runtime.projectRoot;
+                if (localAppPath) {
+                    startTask(`Removing local app files for "${runtime.envName}"...`);
+                    await removePathIfExists(localAppPath, `app files for "${runtime.envName}"`);
+                    succeedTask(`Local app files removed for "${runtime.envName}".`);
+                }
+                else {
+                    printInfo(`No saved local app path found for "${runtime.envName}".`);
+                }
+            }
+            if (removeData) {
+                const configuredStoragePath = resolveConfiguredPath(runtime.env.config.storagePath);
+                if (configuredStoragePath) {
+                    startTask(`Removing storage data for "${runtime.envName}"...`);
+                    await removePathIfExists(configuredStoragePath, `storage data for "${runtime.envName}"`);
+                    succeedTask(`Storage data removed for "${runtime.envName}".`);
+                }
+                else {
+                    printInfo(`No saved storage path found for "${runtime.envName}".`);
+                }
+            }
+            if (removeEnvConfig) {
+                startTask(`Removing saved CLI env config for "${runtime.envName}"...`);
+                const result = await removeEnv(runtime.envName);
+                succeedTask(`Saved CLI env config removed for "${runtime.envName}"${result.currentEnv ? ` (current env: ${result.currentEnv})` : ''}.`);
+            }
+        }
+        catch (error) {
+            failTask(`Failed to bring down NocoBase for "${runtime.envName}".`);
+            this.error(formatDownFailure(runtime.envName, error instanceof Error ? error.message : String(error)));
+        }
+    }
+}