pi-web-ui 0.64.8 → 0.66.0

package/README.md

@@ -163,6 +163,48 @@ silences the warning):
 npm i -g --allow-scripts=node-pty,@google/genai,protobufjs pi-web-ui@latest
 ```
 
+### Termux (Android)
+
+pi-web-ui runs fine on Android via [Termux](https://termux.dev), but `node-pty`
+(the native dependency) needs a toolchain, and Android has a few quirks worth
+knowing:
+
+1. **Install the build toolchain first** — `node-pty` needs Python and a C
+   toolchain:
+
+   ```bash
+   pkg install python clang make binutils
+   ```
+
+2. **Point the node-pty build at a dummy NDK path.** On Android, gyp fails with
+   `Undefined variable android_ndk_path` unless the variable is defined:
+
+   ```bash
+   GYP_DEFINES="android_ndk_path=' '" npm i -g --allow-scripts=node-pty,@google/genai,protobufjs pi-web-ui@latest
+   ```
+
+3. **If `pi-web-ui` won't execute after install** (the exec bit and/or shebang
+   can get mangled on Android): restore it:
+
+   ```bash
+   chmod +x "$(command -v pi-web-ui)"
+   sed -i 's/\r$//' "$(command -v pi-web-ui)"
+   ```
+
+4. **Run it in the background** with `--no-browser` (there is no desktop
+   browser to auto-open):
+
+   ```bash
+   setsid nohup pi-web-ui --no-browser --cwd /path/to/workspace >~/pi-web.log 2>&1 &
+   ```
+
+   `setsid` detaches the server from the launching shell's process group, so
+   closing the Termux session doesn't take the server down — `nohup` alone is
+   not enough when the parent process group gets killed.
+
+The `[control] socket error: EACCES …/.pi-web/pi-web-ui.sock` warning at startup
+is harmless on Android: `pi-web-ui server stop/restart` won't work over the
+control socket, but the web UI itself is unaffected.
 
 ## Quick start
 
@@ -280,6 +322,14 @@ Example — install the webmail plugin:
 pi-web-ui install https://github.com/xing-shuyin/pi-web-ui/tree/main/plugins/webmail
 ```
 
+You can also install from inside the UI: **设置 → 界面插件 → 插件市场** lists
+maintainable plugins (the same set, shipped in `plugins/catalog.json`) with
+full **安装 / 更新 / 卸载** controls (updates keep `config.json`), and lets you
+drop any third-party plugin into the list via **添加插件** (paste `owner/repo`
+or an `owner/repo/subdir` source) — your additions are stored in
+`<dataDir>/plugin-catalog.json`. A plugin author can contribute to the built-in
+list with a one-line PR to `plugins/catalog.json`.
+
 Each plugin's directory in the repo has its own `README.md` with full feature
 lists, configuration and per-plugin caveats.