Directories
¶
| Path | Synopsis |
|---|---|
|
Package api is the llmbox HTTP box-control API: the JSON surface the server exposes for box operations (create/get/list/destroy/logs/exec, proxies, spokes) and a Client that speaks it.
|
Package api is the llmbox HTTP box-control API: the JSON surface the server exposes for box operations (create/get/list/destroy/logs/exec, proxies, spokes) and a Client that speaks it. |
|
Package boxconfig holds the box-provisioning configuration shared by the hub (which fills these from its YAML config) and the spoke (which fills them from command-line flags): the per-box resource caps and the registry credentials, their built-in defaults, and the conversion into the Docker registry auth map the box layer consumes.
|
Package boxconfig holds the box-provisioning configuration shared by the hub (which fills these from its YAML config) and the spoke (which fills them from command-line flags): the per-box resource caps and the registry credentials, their built-in defaults, and the conversion into the Docker registry auth map the box layer consumes. |
|
Package cluster implements llmbox's hub-and-spoke model: a single hub (the MCP front-end the chatbot talks to) drives box operations on one or more spokes, each of which owns a local Docker daemon.
|
Package cluster implements llmbox's hub-and-spoke model: a single hub (the MCP front-end the chatbot talks to) drives box operations on one or more spokes, each of which owns a local Docker daemon. |
|
Package sandbox holds the backend-neutral box lifecycle types shared across llmbox: the inputs and views that cross the hub/spoke boundary and the box-id validation rule.
|
Package sandbox holds the backend-neutral box lifecycle types shared across llmbox: the inputs and views that cross the hub/spoke boundary and the box-id validation rule. |
Click to show internal directories.
Click to hide internal directories.