v2.1.5

t

v2.1.4

fix uninstall: use sudo to remove CLI from /usr/local/bin

v2.1.3

fix entrypoint crash on container restart with LOCKBOX_USER set

- fix: groupmod failed on restart because lockbox group was already
  renamed on first run. Now checks if lockbox group still exists
  before attempting rename.
- test: fix set_env test extraction to work with CLI wrapper guard.

v2.1.2

v2.1.2 - load /etc/environment in SSH sessions

lockbox-wrapper now reads /etc/environment at startup so
Docker env vars (set via -e) are available in SSH sessions.
Combined with the env dump added in v2.1.1, this makes
Docker env vars seamlessly available to all lockbox services.

v2.1.1

v2.1.1 - fix CLI env updates + SSH env visibility

Fixes:
- Generated CLI flag handlers (--port, --memory, --cpus, etc.)
  now work on upgraded installs where .env is missing new keys.
  Replaced sed "s/^KEY=.*/KEY=val/" with set_env() delete+append.

Features:
- Container env vars dumped to /etc/environment so SSH sessions
  can access them.

102 integration tests passing.

v2.1.0

v2.1.0 - complete file operations toolkit

New builtin commands:
- move-file <src> <dst>
- copy-file <src> <dst>
- file-info <path> (JSON output)
- file-exists <path> (true/false)
- file-hash <path> (SHA-256)
- disk-usage [path] (bytes)
- search-files <glob-pattern> (recursive)
- append-file <path> (stdin)

All operations sandboxed to /work with full path traversal
protection. 27 new integration tests added.

v2.0.0

v2.0.0 - LLM-friendly command names

BREAKING CHANGES:
- ls -> list-files
- rm -> remove-file
- mkdir -> create-dir
- rmdir -> remove-dir
- rrmdir -> remove-dir-recursive
- list-files text output simplified to plain filenames
  (directories marked with / suffix, no permissions/owner/size)

Unchanged:
- get, put (same names, same behavior)
- list-files --json (still returns full metadata)
- all security boundaries (path sandboxing, injection prevention)

Why: when AI agents use lockbox as a skill, Linux-style names cause
LLMs to hallucinate flags like ls -la or rm -rf. Descriptive names
eliminate this entirely.

v1.3.0

v1.3.0 - environment support + processing unit selection

New features:
- environment section in installer YAML config for passing env vars
  into containers (container_env mapping, CLI flags, .env defaults)
- built-in --processing-unit flag (cpu, cuda, rocm) in every generated
  installer - no opt-in required, any user can choose at start time
- --gpus flag for GPU device selection (maps to NVIDIA_VISIBLE_DEVICES
  or HIP_VISIBLE_DEVICES depending on processing unit)
- docker-compose.cuda.yml and docker-compose.rocm.yml overlays
  generated automatically, merged by compose() at runtime

Breaking changes:
- CLI flags renamed: -p -> --port, -c -> --cpus, -r -> --memory, -s -> --swap
- gpu: true YAML field removed (processing unit support is now unconditional)

v1.2.1

no more double pull

v1.2.0

support env vars