viberun 0.3.6 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -208,14 +208,14 @@ For the full build/test/E2E flow, see `DEVELOPMENT.md`.
208
208
  ```
209
209
  viberun <app>
210
210
  -> ssh <host>
211
- -> viberun-server <app>
212
- -> docker container viberun-<app>
213
- -> agent session (tmux)
211
+ -> viberun-server gateway (mux)
212
+ -> viberun-server <app>
213
+ -> docker container viberun-<app>
214
+ -> agent session (tmux)
214
215
 
215
216
  container port 8080
216
217
  -> host port (assigned per app)
217
- -> ssh -L localhost:<port>
218
- -> http://localhost:<port>
218
+ -> mux forward -> http://localhost:<port>
219
219
  -> (optional) host proxy (Caddy)
220
220
  -> https://<app>.<domain>
221
221
  ```
@@ -223,7 +223,7 @@ container port 8080
223
223
  ### Core components
224
224
 
225
225
  - Client: `viberun` CLI on your machine.
226
- - Server: `viberun-server` executed on the host via SSH (no long-running daemon required).
226
+ - Server: `viberun-server gateway` executed on the host via SSH (no long-running daemon required).
227
227
  - Container: `viberun-<app>` Docker container built from the `viberun:latest` image.
228
228
  - Agent: runs inside the container in a tmux session (default provider: `codex`).
229
229
  - Host RPC: local Unix socket used by the container to request snapshot/restore operations.
@@ -231,10 +231,10 @@ container port 8080
231
231
 
232
232
  ### Session lifecycle
233
233
 
234
- 1. `viberun <app>` resolves the host (from `@host` or your default config) and runs `viberun-server` over SSH.
234
+ 1. `viberun <app>` resolves the host (from `@host` or your default config) and starts the `viberun-server gateway` over SSH.
235
235
  2. The server creates the container if needed, or starts it if it already exists.
236
236
  3. The agent process is attached via `docker exec` inside a tmux session so it persists across disconnects.
237
- 4. `viberun` sets up a local port forward so you can open the app on `http://localhost:<port>`.
237
+ 4. `viberun` sets up a local mux forward so you can open the app on `http://localhost:<port>`.
238
238
 
239
239
  ### Bootstrap pipeline
240
240
 
@@ -340,7 +340,7 @@ Base skills are shipped in `/opt/viberun/skills` and symlinked into each agent's
340
340
 
341
341
  ### Security model
342
342
 
343
- - All control traffic goes over SSH; the server is invoked on demand and does not expose a network port.
343
+ - All control traffic goes over the mux over SSH; the server is invoked on demand and does not expose a network port.
344
344
  - The host RPC socket is local-only and protected by filesystem permissions and a per-session token.
345
345
  - Containers are isolated by Docker and only the app port is exposed.
346
346
  - App URLs are optional: the proxy requires login by default and can be made public per app with `viberun <app> url --make-public`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "viberun",
3
- "version": "0.3.6",
3
+ "version": "0.4.0",
4
4
  "license": "BSD-3-Clause",
5
5
  "bin": {
6
6
  "viberun": "bin/viberun.js"