@nocobase/plugin-ai 2.2.0-beta.2 → 2.2.0-beta.5

package/dist/ai/docs/nocobase/ai/install-nocobase-app.md

@@ -24,23 +24,36 @@ If you often work with multiple terminals or want to operate in parallel with AI
 
 ## Step 2: Initialize the app
 
-We recommend opening the visual wizard directly:
+We recommend installing through the UI wizard:
 
 ```bash
 nb init --ui
 ```
 
-![2026-06-11-20-14-32](https://static-docs.nocobase.com/2026-06-11-20-14-32.png)
+1. `Getting started` - set the `--env` identifier and choose `Install a new app`
 
-Different setup paths show slightly different steps. If you follow the default `Install a new app` path, you will usually see these six steps:
+![2026-06-11-20-14-32](https://static-docs.nocobase.com/2026-06-11-20-14-32.png)
 
-1. `Getting started` - set the `--env` identifier and choose `Install a new app`
 2. `App environment` - set the app basics, storage location, and runtime port
+
+![2026-06-14-10-03-06](https://static-docs.nocobase.com/2026-06-14-10-03-06.png)
+
 3. `App source and version` - choose how to get the app and which source and version to use
+
+![2026-06-14-09-51-33](https://static-docs.nocobase.com/2026-06-14-09-51-33.png)
+
 4. `Configure the database` - choose the built-in database or a custom database
+
+![2026-06-14-09-52-05](https://static-docs.nocobase.com/2026-06-14-09-52-05.png)
+
 5. `Create an admin account` - set up the first admin account
+
+![2026-06-14-09-52-56](https://static-docs.nocobase.com/2026-06-14-09-52-56.png)
+
 6. `Connection & authentication` - enter the app access URL and choose an authentication method
 
+![2026-06-14-10-00-35](https://static-docs.nocobase.com/2026-06-14-10-00-35.png)
+
 If you prefer terminal interaction, you can also run:
 
 ```bash

package/dist/ai/docs/nocobase/ai/upgrade-from-2-0-to-2-1.md

@@ -0,0 +1,57 @@
+---
+title: NocoBase 2.0 to 2.1 Upgrade Guide
+description: Upgrade a NocoBase 2.0 app to 2.1, including old installation methods, nb CLI options, and the recommended migration path.
+---
+
+# How to Upgrade NocoBase from 2.0 to 2.1
+
+Upgrading from NocoBase 2.0 to NocoBase 2.1 is smooth for the app itself. The bigger change is the NocoBase CLI.
+
+Where:
+
+- In 2.0 and earlier, CLI commands usually start with `yarn nocobase`
+- In 2.1 and later, CLI commands use the globally installed `nb`
+
+Old apps do not have to move to `nb` right away. If you only need to upgrade an already stable NocoBase 2.0 app to 2.1, continue using the original installation and upgrade method by default. For newly installed apps, we recommend using the new `nb` CLI.
+
+## Continue Using the Original Installation and Upgrade Method
+
+If you are already used to the previous installation method, you can keep using it. Follow the original installation and upgrade docs as before.
+
+### Install NocoBase
+
+- [Docker installation](/get-started/installation/docker)
+- [create-nocobase-app installation](/get-started/installation/create-nocobase-app)
+- [Git source installation](/get-started/installation/git)
+
+### Upgrade NocoBase
+
+- [Upgrade a Docker installation](/get-started/upgrading/docker)
+- [Upgrade a create-nocobase-app installation](/get-started/upgrading/create-nocobase-app)
+- [Upgrade a Git source installation](/get-started/upgrading/git)
+
+## Use `nb` CLI for New Apps
+
+For new apps, we recommend the more convenient `nb` installation and upgrade flow.
+
+### Install NocoBase
+
+- [Install NocoBase App](./install-nocobase-app.md)
+
+### Upgrade NocoBase
+
+- [Upgrade NocoBase App](./upgrade-nocobase-app.md)
+
+## How to Migrate to `nb` CLI
+
+If you want to manage apps with `nb` consistently in the future, the more reliable approach for now is to create a new app and migrate the old app data into it.
+
+Migration steps:
+
+1. Create a new CLI app with `nb init`
+2. Migrate the old app's database, `storage`, and required environment variables
+3. After verifying that the new app works properly, switch the production environment over to it
+
+You can also wait for a while. The ability for `nb` to take over existing local apps is still under development.
+
+![2026-06-13-21-29-24](https://static-docs.nocobase.com/2026-06-13-21-29-24.png)

package/dist/ai/docs/nocobase/ai/upgrade-nocobase-app.md

@@ -5,6 +5,12 @@ description: Upgrade a NocoBase app saved as a CLI env with nb app upgrade, incl
 
 # Upgrade NocoBase App
 
+:::tip Scope
+
+This guide applies to apps installed with `nb init`. If your app was installed with the old method, read [How to upgrade NocoBase from 2.0 to 2.1](./upgrade-from-2-0-to-2-1.md) first.
+
+:::
+
 ## Step 1: Confirm the Current Env
 
 ```bash

package/dist/ai/docs/nocobase/api/cli/init.md

@@ -121,7 +121,7 @@ The “Default” below means the value or behavior that `nb init` usually uses
 | `--ui`          | boolean | `false`                                                                      | Open the local browser wizard; cannot be used with `--yes` or `--resume`               |
 | `--verbose`     | boolean | `false`                                                                      | Show detailed command output                                                           |
 | `--skip-skills` | boolean | `false`                                                                      | Skip syncing NocoBase AI coding skills                                                 |
-| `--ui-host`     | string  | `127.0.0.1`                                                                  | Bind address for the `--ui` local service                                              |
+| `--ui-host`     | string  | `127.0.0.1`                                                                  | Browser-accessible host shown in the `--ui` wizard URL; the local service always listens on `0.0.0.0` |
 | `--ui-port`     | integer | `0`                                                                          | Port for the `--ui` local service; `0` means automatic assignment                      |
 | `--locale`      | string  | Follows `NB_LOCALE`, CLI config, or system locale; final fallback is `en-US` | Language for CLI prompts and the local setup UI: `en-US` or `zh-CN`                    |
 | `--resume`      | boolean | `false`                                                                      | Continue the last unfinished initialization and reuse the saved workspace env config   |

package/dist/ai/docs/nocobase/api/cli/skills/install.md

@@ -27,6 +27,7 @@ nb skills install [flags]
 ```bash
 nb skills install
 nb skills install --yes
+nb skills install --verbose
 nb skills install --json
 ```
 

package/dist/ai/docs/nocobase/api/cli/skills/update.md

@@ -27,6 +27,7 @@ nb skills update [flags]
 ```bash
 nb skills update
 nb skills update --yes
+nb skills update --verbose
 nb skills update --json
 ```
 

package/dist/ai/docs/nocobase/get-started/deployment/how-to-deploy-nocobase-faster.mdx

@@ -116,7 +116,7 @@ When users access NocoBase, requests go directly to your server. An appropriate
 - Disadvantages: This method is simple but performs poorly when handling high concurrency or static files; suitable for development and testing only.
 - Recommendation: Please avoid this method if possible.
 
-> Reference "[Installation Documentation](https://v2.docs.nocobase.com/get-started/quickstart)"
+> Reference "[Installation Documentation](https://docs.nocobase.com/get-started/quickstart)"
 
 Without a reverse proxy, homepage loading takes about 6.1 seconds
 ![20250409131357](https://static-docs.nocobase.com/20250409131357.png)
@@ -126,7 +126,7 @@ Without a reverse proxy, homepage loading takes about 6.1 seconds
 - Advantages: Reverse proxy servers can efficiently handle concurrent connections, serve static files, implement load balancing, and make HTTP/2 configuration simple.
 - Recommendation: In production environments, after application deployment (source code deployment / create-nocobase-app / Docker image), use Nginx or Caddy as a reverse proxy.
 
-> Reference "[Deployment Documentation](https://v2.docs.nocobase.com/get-started/deployment/production)"
+> Reference "[Deployment Documentation](https://docs.nocobase.com/get-started/deployment/production)"
 
 With Nginx proxy, homepage loading takes about 3-4 seconds
 ![20250409131541](https://static-docs.nocobase.com/20250409131541.png)

package/dist/ai/docs/nocobase/interface-builder/blocks/data-blocks/map.md

@@ -0,0 +1,105 @@
+---
+pkg: '@nocobase/plugin-map'
+title: 'Map Block'
+description: 'The Map block displays collection records on AMap or Google Maps, and supports point, line, polygon, and circle fields.'
+keywords: 'Map Block,AMap,Google Maps,Point,Line,Polygon,Circle,NocoBase'
+---
+
+# Map block
+
+## Introduction
+
+The Map block displays geographic data from a collection on a map. It is suitable for scenarios such as store locations, customer addresses, device distribution, route tracking, and area management.
+
+The Map block supports AMap and Google Maps. It can render point, line, polygon, and circle fields, and can open record views or run block actions from map overlays.
+
+![Map block interface](https://static-docs.nocobase.com/20260615162922.png)
+
+## Installation
+
+The Map block is provided by the built-in `@nocobase/plugin-map` plugin. Enable the plugin before adding the block.
+
+After enabling the plugin, go to "Plugin settings / Map manager" and configure the map provider:
+
+- **AMap**: configure `Access key`, plus `securityJsCode` or `serviceHost`
+- **Google Maps**: configure `Api key`
+
+If the map cannot be loaded, check whether the key is valid, whether the domain whitelist includes the current access domain, and whether the browser can access the selected map provider.
+
+## Prepare map fields
+
+Before adding a Map block, create at least one map field in the target collection. You can find these field types in the "Map-based geometry" group:
+
+| Field type | Usage                                                                 |
+| ---------- | --------------------------------------------------------------------- |
+| Point      | Marks a single location, such as a store, device, or customer address |
+| Line       | Represents a route or track                                           |
+| Polygon    | Represents an area                                                    |
+| Circle     | Represents a radius around a center point                             |
+
+When creating the field, choose the "Map type". This determines whether the field editor and the block use AMap or Google Maps.
+
+## Add block
+
+In page configuration mode, click "Add block" and choose "Map" from "Data Blocks".
+
+![Add a Map block from Data Blocks](https://static-docs.nocobase.com/20260615163017.png)
+
+When creating the block, configure:
+
+1. Select the collection to display.
+2. Select the "Map field" used to draw map overlays. It can be a field in the current collection or a map field reached through an association field.
+3. Optionally select the "Marker field". When the map field is a point field, this field is used as the point label.
+
+If the collection has no available map field, the "Map field" selector will be empty. Add a point, line, polygon, or circle field to the collection first.
+
+## Block settings
+
+### Map field and marker field
+
+Used to change the map field displayed by the block and the marker label field.
+
+The marker field only applies to point fields. It is usually a text field such as name, address, or code.
+
+### Data scope
+
+Used to restrict the records displayed in the Map block.
+
+For large datasets, configure a data scope or add filter actions to narrow the displayed records. The Map block loads all records that match the data scope without pagination.
+
+For more details, see: [Set Data Scope](/interface-builder/blocks/block-settings/data-scope)
+
+### Concatenation order field
+
+Used to sort point records and connect them into a route.
+
+This setting only takes effect when the map field is a point field.
+
+### Default zoom level
+
+Used to set the initial zoom level of the map.
+
+## Actions
+
+The Map block supports adding actions at the top of the block, such as:
+
+- Filter
+- Add new
+- Popup
+- Link
+- Refresh
+- Custom request
+- AI employee
+- JS action
+
+Clicking a map overlay triggers the record opening flow, which is usually used to open a popup, drawer, or another record view.
+
+## Select records
+
+The Map block provides selection tools in the upper-left corner:
+
+- Location icon: exits selection mode and returns to normal viewing
+- Selection icon: enters selection mode and lets you draw a polygon area on the map
+- Confirm icon: confirms the current selection area and adds records inside it to the selected state
+
+Selected records are synced to the block resource and can be used by later block actions.

package/dist/ai/docs/nocobase/nocobase-cli/installation/cli.md

@@ -48,7 +48,7 @@ Replace `<server-ip>` with the actual IP of the current server that is accessibl
 
 Generally speaking:
 
-- `default-ui-host` is used for the default listening address of `nb init --ui` when starting the wizard page
+- `default-ui-host` is used to generate the browser-accessible URL for the `nb init --ui` wizard; the wizard service itself always listens on `0.0.0.0`
 - `default-api-host` for the API address generated by default on new installations
 
 If deployed on a server, both values ​​should usually be changed to IPs accessible to the current server, rather than continuing to use the default local address.

package/dist/ai/docs/nocobase/ops-management/backup-manager/index.mdx

@@ -8,18 +8,20 @@ pkg: '@nocobase/plugin-backups'
 
 The NocoBase backup manager plugin provides features for fully backing up of the NocoBase database and user uploaded files, including backup's scheduling, downloading, deleting, and restoring operation.
 
-:::warning
-The Backup Manager plugin is included in the Professional and Enterprise editions. For Community and Standard edition users, you can directly back up the database; see details at: [`How to Backup and Restore NocoBase`](https://www.nocobase.com/en/blog/nocobase-backup-restore)
-:::
-
 ## Install Database Client
 
-The Backup Manager depends on the client for the corresponding database. Before use, please visit the official website to download the client that matches your database version:
+Backup Manager depends on the database client for the primary database. Before use, confirm that the current runtime environment has a client that matches your database version.
+
+:::tip
+When installing NocoBase with Docker, use the corresponding `full` image when possible, such as `latest-full`, `beta-full`, or `alpha-full`. These images already include common database clients, so manual installation is usually not required.
+:::
+
+If the current environment does not have the required database client, download the client that matches your database version from the official website:
 
 - MySQL: https://dev.mysql.com/downloads/
 - PostgreSQL: https://www.postgresql.org/download/
 
-For Docker versions, you can directly write a script in the `./storage/scripts` directory
+If you need to install it manually in a Docker environment, you can write a script in the `./storage/scripts` directory:
 
 ```bash
 mkdir ./storage/scripts
@@ -188,4 +190,4 @@ Switch to the "Settings" tab, modify the backup settings, and click `Save` to ta
 - `Backup local storage files`: Whether to include files uploaded by users to the server's local storage (storage/uploads) in the backup.
 - `Restore password`: If a restore password is set, it must be entered when restoring the backup.
 
-> **Please keep the restore password safe. Forgetting the password will make it impossible to restore the backup file.**
+> **Please keep the restore password safe. Forgetting the password will make it impossible to restore the backup file.**