instabox 0.8.86 → 0.8.88

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/cli/SHA256SUMS CHANGED
@@ -1,6 +1,6 @@
1
- 706e27a5f18aac28da9ad0c8a91c5b754a08d252a785cdb1088066e3117e9eea instabox-darwin-amd64
2
- 6e46b687767eea5b1dd2a11f1fbb6a2b89fc1845852362795ac144fd90af8bb9 instabox-darwin-arm64
3
- fa6fc376367aa7f78f9c07f6447be5ddc3e80246758aa017f0e5eea5a5f7dc61 instabox-linux-amd64
4
- 8c7bd54dcc9e2059285b99ca54325773beefe393303b366c5d6c0d0ec5293c2a instabox-linux-arm64
5
- fec462e6acd94c9bbefa3741feb561af03f592f2f24a46e4be3b96e94e16e352 instabox-windows-amd64.exe
6
- 5974e8916ac31adbc181c3f07d19ffb7c8c5f87b31c124e88e4676bf58b3b77f instabox-windows-arm64.exe
1
+ 0b50d43aa21917481144361b0ab38510359ffad5f3a2bd168d18ca9145e146a0 instabox-darwin-amd64
2
+ c2040f967a48b2a35f95212ad83e42291a5ab12677e50cf5f55e328fea7bc9f3 instabox-darwin-arm64
3
+ ac483af299bf77d76c8989116b9a735fd991cdf82f86762fdec5b1890c220b10 instabox-linux-amd64
4
+ e695bf4d28b6460f64c1e822649f663288ae18ff979b13d4e13ea9d28adc3a1d instabox-linux-arm64
5
+ 8f46f1b3e668a759ce5e9ce22ccce5387048eee81d899fdafb41c7c99899643b instabox-windows-amd64.exe
6
+ f60dc5928b4a1a280625ff24586ad1d673903f781673f930b261ff29c7d5c7ab instabox-windows-arm64.exe
Binary file
Binary file
Binary file
Binary file
Binary file
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "instabox",
3
- "version": "0.8.86",
3
+ "version": "0.8.88",
4
4
  "description": "A cloud box for your coding agent, the instabox CLI and its agent skills in one command: npx instabox@latest",
5
5
  "type": "module",
6
6
  "bin": {
@@ -69,6 +69,7 @@ instabox files work /data/home # list a directory (or print a t
69
69
  instabox push work ./app # copy a file or directory in (to /data/home/app)
70
70
  instabox pull work /data/home/app/out.log # copy a file or directory out (to ./out.log)
71
71
  instabox cp ./x.tgz work:/data/home/x.tgz # scp-style, either way (cp work:/data/home/x.tgz .)
72
+ instabox push work ./app/ /data/home/app # trailing / (or /.): app's files into /data/home/app, no app/app
72
73
  instabox auto-suspend work 10m # idle time before a paid box pauses
73
74
  instabox max-run work 120 # pause a paid box after two running hours
74
75
  instabox max-run work -1 # remove the runtime cap; idle policy still applies
@@ -80,6 +81,7 @@ instabox rm --yes work # delete the box (without --yes
80
81
  ```
81
82
 
82
83
  - Names or IDs (`m_...`) both work wherever `<id-or-name>` is accepted.
84
+ - Directories in `push`, `pull` and `cp` (both directions) follow `cp -r`/rsync: `SRC` into an existing directory lands as `DST/<name>` (`push work ./app /data/home` gives `/data/home/app`); `SRC` to a missing path becomes it; `SRC/`, `SRC/.` or `.` copies the contents into `DST` itself, creating it if missing (`pull work /data/home/app/ ./app` fills `./app`). With the destination omitted a directory always keeps its name (`push work .` gives `/data/home/<dirname>`), so nothing merges into HOME or the cwd by default.
83
85
  - For large uploads use `instabox push` or `instabox cp` (the HTTP API, parallel-friendly), not scp or rsync over `ssh.instabox.sh`, which keeps about 2 MiB in flight per connection and so slows with distance. Measured: at a 5 ms round trip both paths do ~104 MB/s; at 305 ms the API does 11-13 MB/s per stream and SSH 3-6 MB/s; 4 parallel API PUTs did 39 MB/s total.
84
86
  - `create` options: `--template T` or `--snapshot S`, `--vcpus N --mem-mib M` (a size of the plan, see Sizes), `--auto-suspend D|0`, `--max-run-minutes N`, `--delete-after D` (delete it D after creation, 1m-24h, whatever its state), `--meta K=V`, `--org O`, `--secrets all|NAME,NAME|none`, `--no-wait`, `--setup-file PATH|-` (`--wait-setup`), `--fail-fast` (when no host has room, fail at once and create nothing instead of failing the create after; with `--snapshot`, instead of creating it stopped).
85
87
  - `create --setup-file PATH` (`-`: stdin; at most 64 KB) runs that script in the new box once it is running, in HOME as the box's user (by its `#!` line, else with bash; CRLF line endings become LF), and prints its output; it replaces create + push + exec for provisioning. A failing script makes `create` exit with the script's code and keeps the box: debug it with `instabox exec work -- /tmp/instabox-setup.sh`. With `--json` the sandbox object gets a `setup` object (`exitCode`, `stdout`, `stderr`, `signal`, `timedOut`, `truncated`, `durationMs`). `create` always waits for the script (`--wait-setup` names that; `=false` is refused) and keeps its state in the box's metadata, so `instabox get work --json` shows it later: `metadata.setupStatus` (`pending`, `running`, `succeeded`, `failed`), `setupExitCode` (`124`: timed out) and `setupLog` (the last 512 characters of its stdout then stderr). The script is killed after `--setup-timeout` (default and at most 10m); for longer installs, use `ssh`. A missing, empty or over-64 KB file is refused before any box is created. `run --setup-file` does the same before its command, with its `-e` variables; when the script fails, run's `--json` `exitCode` is the script's. The script stays at `/tmp/instabox-setup.sh` (and in snapshots), so keep credentials out of it.