nterminal 1.2.1 → 1.2.2

package/README.md

@@ -22,18 +22,20 @@ Browser
 
 ## Quick Start
 
-Clone the repo on the machine that should become the **main server**, then run:
+Install NTerminal on the machine that should become the **main server**, then run:
 
 ```bash
-npm run onboarding
+npm install -g nterminal
+nterminal onboarding
 ```
 
 Choose `main`. Onboarding installs dependencies, writes `.env`, creates secrets, sets your password and TOTP, and can build/start the service.
 
-To add another machine, clone the repo there and run the same command:
+To add another machine, install NTerminal there and run the same command:
 
 ```bash
-npm run onboarding
+npm install -g nterminal
+nterminal onboarding
 ```
 
 Choose `secondary`, enter the main server URL, log in once from the CLI, and the server registers itself in the main UI.
@@ -42,15 +44,14 @@ After onboarding finishes, open the URL printed in the final summary and log in
 
 See [docs/onboarding.md](docs/onboarding.md) for the full main/secondary setup flow, nginx/TLS automation, and local-only setup.
 
-After NTerminal is published to npm, package installs can use:
+For source checkouts, clone the repo and run the npm script instead:
 
 ```bash
-npm install -g nterminal
-nterminal onboarding
+npm run onboarding
 ```
 
-Package installs keep runtime config and state under `~/.nterminal` so package updates do not overwrite local sessions or secrets.
-Use a user-writable npm global prefix if you want in-app updates to run without sudo.
+The source script runs the same onboarding flow through the local checkout.
+Package installs keep runtime config and state under `~/.nterminal` so package updates do not overwrite local sessions or secrets. Use a user-writable npm global prefix if you want in-app updates to run without sudo.
 
 ## Key Features
 
@@ -108,8 +109,8 @@ Use a user-writable npm global prefix if you want in-app updates to run without
 ### Simple npm Toolchain
 
 - The project uses npm so source checkouts and package installs use the same package manager.
-- `npm run onboarding` runs install automatically on fresh checkouts.
-- The `nterminal` CLI entrypoint is prepared for global npm installs.
+- `nterminal onboarding` runs the guided setup for npm package installs.
+- `npm run onboarding` runs the same setup from a source checkout and installs dependencies automatically.
 
 ## Requirements
 
@@ -126,6 +127,17 @@ npm rebuild node-pty --build-from-source
 
 ## Common Commands
 
+For npm package installs:
+
+```bash
+nterminal onboarding
+nterminal status
+nterminal logs
+nterminal restart
+```
+
+For source checkouts:
+
 ```bash
 npm run onboarding
 npm run service:status

package/docs/configuration.md

@@ -19,7 +19,13 @@ npm run generate:secrets
 
 Paste the generated `NTERMINAL_SESSION_SECRET=...` value into `.env`.
 
-For normal installs, prefer:
+For normal package installs, prefer:
+
+```bash
+nterminal onboarding
+```
+
+For source checkouts:
 
 ```bash
 npm run onboarding

package/docs/onboarding.md

@@ -1,28 +1,30 @@
 # Onboarding
 
-NTerminal uses one interactive command for both the main server and secondary servers:
+NTerminal uses one interactive command for both the main server and secondary servers.
+
+For npm package installs:
 
 ```bash
-npm run onboarding
+npm install -g nterminal
+nterminal onboarding
 ```
 
-`npm install` runs automatically as the `preonboarding` hook, so a fresh checkout does not need a separate install step.
+CLI package installs store `.env`, state, pid, and log files under `~/.nterminal`. Install with a user-writable npm global prefix so in-app updates can run `npm install -g nterminal@latest` without sudo.
 
-After npm publication, package installs use the CLI directly:
+For source checkouts:
 
 ```bash
-npm install -g nterminal
-nterminal onboarding
+npm run onboarding
 ```
 
-CLI package installs store `.env`, state, pid, and log files under `~/.nterminal`. Install with a user-writable npm global prefix so in-app updates can run `npm install -g nterminal@latest` without sudo.
+`npm install` runs automatically as the `preonboarding` hook, so a fresh checkout does not need a separate install step.
 
 ## Main Server
 
 Run onboarding on the machine that should serve the browser UI:
 
 ```bash
-npm run onboarding
+nterminal onboarding
 ```
 
 Choose `main`.
@@ -43,7 +45,7 @@ The final summary prints the public URL, internal bind, and next steps.
 Run onboarding on each additional machine that should appear in the main UI:
 
 ```bash
-npm run onboarding
+nterminal onboarding
 ```
 
 Choose `secondary`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nterminal",
-  "version": "1.2.1",
+  "version": "1.2.2",
   "license": "GPL-3.0-only",
   "type": "module",
   "packageManager": "npm@10.9.7",