@fui-org/fui-cli 1.3.1 → 2.0.0

package/README.md

@@ -1,6 +1,6 @@
 # fui
 
-A command-line tool for the FUI low-code platform: projects, modules, components, imports, users, rights, database connections, SQL, schema and stored procedures. It works with AI agents (Claude Code, Codex, Antigravity) and replaces the Fui MCP server.
+A command-line tool for the FUI low-code platform: projects, modules, components, imports, users, rights, database connections, SQL, schema and stored procedures. It works with AI agents (Claude Code, Codex, Antigravity).
 
 ## Install
 
@@ -81,12 +81,14 @@ fui file status
 
 ## Workspace location
 
-`fui` keeps projects in `~/.fui-mcp/workspaces`, the same folder Fui MCP uses. To use another folder:
+`fui` keeps projects in `~/.fui/workspaces`. To use another folder:
 
 ```bash
 fui config set workdir ~/work/fui
 ```
 
+The files in a workspace are described in [docs/workspace-format.md](docs/workspace-format.md).
+
 ## Database connections
 
 Secrets are read only from stdin (`-`) or from an env var (`--*-env VAR`):
@@ -97,7 +99,21 @@ fui db add local -p demo --conn-env SQLITE_URL
 fui db list
 ```
 
-A connection is an MSSQL string (through tAPI) or a `sqlite://` URL.
+A connection is an MSSQL string (through tAPI) or a `sqlite://` URL. `fui db add <apiName>` saves it under a readable
+connection name (`--name`, suggested from the apiName and zone otherwise) in `_db/_connections.json` version 2.
+
+## Coming from Fui MCP
+
+`fui` does not read Fui MCP's settings. Point it at your workspace and set the API once:
+
+```bash
+fui config set workdir <your Fui MCP workspace folder>
+fui config set api-base https://<fui-api-host>
+printf %s "$FUI_TOKEN" | fui config set api-token -
+```
+
+Connection files from before the multi-zone layout (`_connections.json` without `"version": 2`) stop DB commands with a
+hint; convert them once with `fui db migrate` (the old file is kept in `_history/`).
 
 ## Uninstall